summaryrefslogtreecommitdiff
path: root/security
diff options
context:
space:
mode:
authorShakeel Butt <shakeelb@google.com>2022-01-24 21:17:36 -0800
committerJens Axboe <axboe@kernel.dk>2022-02-07 08:44:01 -0700
commit0a3f1e0beacf6cc8ae5f846b0641c1df476e83d6 (patch)
tree50d13631aa49f0bb59a172c1d27f15699d2aa5ad /security
parent0d7c1153d9291197c1dc473cfaade77acb874b4b (diff)
mm: io_uring: allow oom-killer from io_uring_setupio_uring-5.17-2022-02-11
On an overcommitted system which is running multiple workloads of varying priorities, it is preferred to trigger an oom-killer to kill a low priority workload than to let the high priority workload receiving ENOMEMs. On our memory overcommitted systems, we are seeing a lot of ENOMEMs instead of oom-kills because io_uring_setup callchain is using __GFP_NORETRY gfp flag which avoids the oom-killer. Let's remove it and allow the oom-killer to kill a lower priority job. Signed-off-by: Shakeel Butt <shakeelb@google.com> Link: https://lore.kernel.org/r/20220125051736.2981459-1-shakeelb@google.com Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions