diff options
| author | Alan Somers <asomers@FreeBSD.org> | 2021-01-10 03:23:05 +0000 |
|---|---|---|
| committer | Alan Somers <asomers@FreeBSD.org> | 2021-01-12 02:53:01 +0000 |
| commit | ff1a307801994e18a87929898225f09d31f3e1fa (patch) | |
| tree | e7d272e3acf2cb11e23b6f91a4881e0a3653de62 /sys/sys/module_khelp.h | |
| parent | 292808246db702b9194deb8938e40fd06914aea9 (diff) | |
| download | src-ff1a307801994e18a87929898225f09d31f3e1fa.tar.gz src-ff1a307801994e18a87929898225f09d31f3e1fa.zip | |
lio_listio: validate aio_lio_opcode
Previously, we would accept any kind of LIO_* opcode, including ones
that were intended for in-kernel use only like LIO_SYNC (which is not
defined in userland). The situation became more serious with
022ca2fc7fe08d51f33a1d23a9be49e6d132914e. After that revision, setting
aio_lio_opcode to LIO_WRITEV or LIO_READV would trigger an assertion.
Note that POSIX does not specify what should happen if aio_lio_opcode is
invalid.
MFC-with: 022ca2fc7fe08d51f33a1d23a9be49e6d132914e
Reviewed by: jhb, tmunro, 0mp
Differential Revision: <https://reviews.freebsd.org/D28078
Diffstat (limited to 'sys/sys/module_khelp.h')
0 files changed, 0 insertions, 0 deletions