From: Waiman Long <longman@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>,
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>,
Phil Auld <pauld@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH-tip] sched: Don't call kfree() in do_set_cpus_allowed()
Date: Mon, 21 Nov 2022 10:04:33 -0500 [thread overview]
Message-ID: <601640d0-9dc2-a060-e165-c8efac54aa34@redhat.com> (raw)
In-Reply-To: <Y3tVPjAjE9OFRLaP@hirez.programming.kicks-ass.net>
On 11/21/22 05:38, Peter Zijlstra wrote:
> On Fri, Nov 18, 2022 at 02:33:02PM -0500, Waiman Long wrote:
>> Commit 851a723e45d1 ("sched: Always clear user_cpus_ptr in
>> do_set_cpus_allowed()") may call kfree() if user_cpus_ptr was previously
>> set. Unfortunately, some of the callers of do_set_cpus_allowed()
> 'some' ? There's only 3 or so, which one triggers this?
It happenned at __kthread_bind_mask() where do_set_cpus_allowed() is
called with pi_lock held.
[ 1084.820105] <TASK>
[ 1084.820110] dump_stack_lvl+0x57/0x81
[ 1084.820117] check_noncircular+0x103/0x120
[ 10[ 1084.820160] lock_acquire+0xba/0x230
[ 1084.820164] ? kfree+0x10f/0x380
[ 1084.820172] ? do_set_cpus_allowed+0x40/0x60
[ 1084.820181] rt_spin_lock+0x27/0xe0
[ 1084.820184] ? kfree+0x10f/0x380
[ 1084.820188] kfree+0x10f/0x380
[ 1084.820195] do_set_cpus_allowed+0x40/0x60
[ 1084.820203] kthread_bind_mask+0x4a/0x70
[ 1084.820211] create_worker+0xfb/0x1a0
[ 1084.820220] worker_thread+0x2e3/0x3c0
[ 1084.820226] ? process_one_work+0x450/0x450
[ 1084.820230] kthread+0x111/0x130
[ 1084.820236] ? kthread_complete_and_exit+0x20/0x20
[ 1084.820244] ret_from_fork+0x22/0x30
[ 1084.820258] </TASK>
[ 1084.820260] BUG: sleeping function called from invalid context at
kernel/locking/spinlock_rt.c:46
It shows up with PREEMPT_RT kernel.
>
>> may not be in a context where kfree() can be safely called. So the
>> following splats may be printed:
>>
>> WARNING: possible circular locking dependency detected
>> BUG: sleeping function called from invalid context
>>
>> To avoid these problems without leaking memory, the free cpumask is now
>> put into a lockless list to be reused in a later sched_setaffinity()
>> call instead.
> Urgh.. depending on which of the callsites it is, it's probably simpler
> to just rework the caller to not use do_set_cpus_allowed(), no?
Maybe. One thing that I am not clear about is why user_cpus_ptr is set
in the first place.
Cheers,
Longman
next prev parent reply other threads:[~2022-11-21 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 19:33 [PATCH-tip] sched: Don't call kfree() in do_set_cpus_allowed() Waiman Long
2022-11-21 10:38 ` Peter Zijlstra
2022-11-21 15:04 ` Waiman Long [this message]
2022-11-22 12:37 ` Peter Zijlstra
2022-11-22 15:23 ` Waiman Long
2022-11-22 16:33 ` Paul E. McKenney
2022-11-22 19:24 ` Peter Zijlstra
2022-11-22 19:30 ` Waiman Long
2022-11-22 19:58 ` Peter Zijlstra
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=601640d0-9dc2-a060-e165-c8efac54aa34@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=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).