Alan Somers ff1a307801 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 022ca2fc7f. 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: 022ca2fc7f Reviewed by: jhb, tmunro, 0mp Differential Revision: <https://reviews.freebsd.org/D28078		2021-01-11 19:53:01 -07:00
..
aio_kqueue_test.c	Revert r337929	2018-08-16 22:04:00 +00:00
aio_test.c	aio: fix the tests when ZFS is not available	2021-01-09 17:16:38 -07:00
lio_kqueue_test.c	Revert r337929	2018-08-16 22:04:00 +00:00
lio_test.c	lio_listio: validate aio_lio_opcode	2021-01-11 19:53:01 -07:00
local.h	Print out when unsafe AIO is enabled to debugging purposes	2017-05-09 19:20:02 +00:00
Makefile	Do a sweep and remove most WARNS=6 settings	2020-10-01 01:10:51 +00:00
Makefile.depend	DIRDEPS_BUILD: Update dependencies.	2017-10-31 00:07:04 +00:00