diff options
| author |   Jens Axboe <axboe@kernel.dk> | 2019-03-14 16:30:06 -0600 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2019-03-18 10:44:44 -0600 |
| commit | fd6fab2cb78d3b6023c26ec53e0aa6f0b477d2f7 (patch) | |
| tree | 6f30a949748bf44ad926b9331cfa27556e9715cd /MAINTAINERS | |
| parent | io_uring: fix poll races (diff) | |
| download | linux-dev-fd6fab2cb78d3b6023c26ec53e0aa6f0b477d2f7.tar.xz linux-dev-fd6fab2cb78d3b6023c26ec53e0aa6f0b477d2f7.zip | |
io_uring: retry bulk slab allocs as single allocs
I've seen cases where bulk alloc fails, since the bulk alloc API
is all-or-nothing - either we get the number we ask for, or it
returns 0 as number of entries.
If we fail a batch bulk alloc, retry a "normal" kmem_cache_alloc()
and just use that instead of failing with -EAGAIN.
While in there, ensure we use GFP_KERNEL. That was an oversight in
the original code, when we switched away from GFP_ATOMIC.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions