[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221231041120.440785-1-longman@redhat.com>
Date: Fri, 30 Dec 2022 23:11:18 -0500
From: Waiman Long <longman@...hat.com>
To: Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Juri Lelli <juri.lelli@...hat.com>,
Vincent Guittot <vincent.guittot@...aro.org>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Steven Rostedt <rostedt@...dmis.org>,
Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
Daniel Bristot de Oliveira <bristot@...hat.com>,
Valentin Schneider <vschneid@...hat.com>
Cc: Phil Auld <pauld@...hat.com>,
Wenjie Li <wenjieli@....qualcomm.com>,
David Wang 王标
<wangbiao3@...omi.com>, Quentin Perret <qperret@...gle.com>,
Will Deacon <will@...nel.org>, linux-kernel@...r.kernel.org,
Waiman Long <longman@...hat.com>
Subject: [PATCH v6 0/2] sched: Fix dup_user_cpus_ptr() & do_set_cpus_allowed() bugs
v6:
- Update patch 2 to fix build error with !CONFIG_SMP configs.
v5:
- Add an alloc_user_cpus_ptr() helper and use it in patch 2.
v4:
- Make sure user_cpus_ptr allocation size is large enough for
rcu_head.
This series fixes a UAF bug in dup_user_cpus_ptr() and uses kfree_rcu()
in do_set_cpus_allowed to avoid lockdep splats.
Waiman Long (2):
sched: Fix use-after-free bug in dup_user_cpus_ptr()
sched: Use kfree_rcu() in do_set_cpus_allowed()
kernel/sched/core.c | 65 +++++++++++++++++++++++++++++++++++++++------
1 file changed, 57 insertions(+), 8 deletions(-)
--
2.31.1
Powered by blists - more mailing lists