lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 16 Aug 2020 17:31:46 -0700 From: Davidlohr Bueso <dave@...olabs.net> To: akpm@...ux-foundation.org Cc: oleg@...hat.com, axboe@...nel.dk, linux-kernel@...r.kernel.org, Davidlohr Bueso <dave@...olabs.net> Subject: [PATCH -next 0/2] tasklist_lock vs get/set priority syscalls Hi, This is a (late) update on trying to reduce some of the scope of the tasklist_lock for get/setpriority(2) as well as the block io equivalent. This version addresses Oleg's previous concerns and incorporates his feedback. Changes from v1: https://lore.kernel.org/lkml/20200512000353.23653-1-dave@stgolabs.net/ - only take the lock for PGID cases. - drop bogus PF_EXITING checks (and live with the small exit race). - add patch for IOPRIO_WHO_PGRP. Please consider for v5.10. Thanks! Davidlohr Bueso (2): kernel/sys: only take tasklist_lock for get/setpriority(PRIO_PGRP) block: fix ioprio_get/set(IOPRIO_WHO_PGRP) vs setuid(2) block/ioprio.c | 4 ++++ kernel/sys.c | 16 ++++++++-------- 2 files changed, 12 insertions(+), 8 deletions(-) -- 2.26.2
Powered by blists - more mailing lists