From: Waiman Long <longman@redhat.com>
To: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>
Cc: "Phil Auld" <pauld@redhat.com>,
"Wenjie Li" <wenjieli@qti.qualcomm.com>,
"David Wang 王标" <wangbiao3@xiaomi.com>,
"Quentin Perret" <qperret@google.com>,
"Will Deacon" <will@kernel.org>,
linux-kernel@vger.kernel.org, "Waiman Long" <longman@redhat.com>
Subject: [PATCH v6 0/2] sched: Fix dup_user_cpus_ptr() & do_set_cpus_allowed() bugs
Date: Fri, 30 Dec 2022 23:11:18 -0500 [thread overview]
Message-ID: <20221231041120.440785-1-longman@redhat.com> (raw)
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
next reply other threads:[~2022-12-31 4:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 4:11 Waiman Long [this message]
2022-12-31 4:11 ` [PATCH v6 1/2] sched: Fix use-after-free bug in dup_user_cpus_ptr() Waiman Long
2023-01-09 10:45 ` [tip: sched/urgent] sched/core: " tip-bot2 for Waiman Long
2023-01-10 13:03 ` [PATCH v6 1/2] sched: " Will Deacon
2022-12-31 4:11 ` [PATCH v6 2/2] sched: Use kfree_rcu() in do_set_cpus_allowed() Waiman Long
2023-01-09 10:45 ` [tip: sched/urgent] sched/core: " tip-bot2 for Waiman Long
2023-01-15 15:54 ` [PATCH v6 2/2] sched: " kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221231041120.440785-1-longman@redhat.com \
--to=longman@redhat.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=qperret@google.com \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=wangbiao3@xiaomi.com \
--cc=wenjieli@qti.qualcomm.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.