diff options
| author | Jens Axboe <axboe@kernel.dk> | 2023-10-03 09:59:58 -0600 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2023-10-03 09:59:58 -0600 |
| commit | 223ef474316466e9f61f6e0064f3a6fe4923a2c5 (patch) | |
| tree | e8122f431d702465945486b5a3861571414b6a9d /io_uring/io-wq.c | |
| parent | 1658633c04653578429ff5dfc62fdc159203a8f2 (diff) | |
| download | linux-223ef474316466e9f61f6e0064f3a6fe4923a2c5.tar.gz linux-223ef474316466e9f61f6e0064f3a6fe4923a2c5.tar.bz2 linux-223ef474316466e9f61f6e0064f3a6fe4923a2c5.zip | |
io_uring: don't allow IORING_SETUP_NO_MMAP rings on highmem pages
On at least arm32, but presumably any arch with highmem, if the
application passes in memory that resides in highmem for the rings,
then we should fail that ring creation. We fail it with -EINVAL, which
is what kernels that don't support IORING_SETUP_NO_MMAP will do as well.
Cc: stable@vger.kernel.org
Fixes: 03d89a2de25b ("io_uring: support for user allocated memory for rings/sqes")
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'io_uring/io-wq.c')
0 files changed, 0 insertions, 0 deletions