From: Oleg Nesterov <oleg@redhat.com>
To: Wander Lairson Costa <wander@redhat.com>
Cc: "Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
Brian Cain <bcain@quicinc.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Stafford Horne <shorne@gmail.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andrei Vagin <avagin@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Daniel Bristot de Oliveira <bristot@kernel.org>,
Yu Zhao <yuzhao@google.com>, Alexey Gladkov <legion@kernel.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
Yang Shi <shy828301@gmail.com>,
open list <linux-kernel@vger.kernel.org>,
Hu Chunyu <chuhu@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
Luis Goncalves <lgoncalv@redhat.com>
Subject: Re: [PATCH v9] kernel/fork: beware of __put_task_struct calling context
Date: Mon, 29 May 2023 14:22:56 +0200 [thread overview]
Message-ID: <20230529122256.GA588@redhat.com> (raw)
In-Reply-To: <CAAq0SUkE_4qF5RuWE7MxnzcbchE4SHkyMvJxHAQeJ+=ZTEwdgg@mail.gmail.com>
On 05/17, Wander Lairson Costa wrote:
>
> On Wed, May 17, 2023 at 12:26 PM Oleg Nesterov <oleg@redhat.com> wrote:
> >
> > LGTM but we still need to understand the possible problems with CONFIG_PROVE_RAW_LOCK_NESTING ...
> >
> > Again, I'll try to investigate when I have time although I am not sure I can really help.
> >
> > Perhaps you too can try to do this ? ;)
> >
>
> FWIW, I tested this patch with CONFIG_PROVE_LOCK_NESTING in RT and
> stock kernels. No splat happened.
Strange... FYI, I am running the kernel with this patch
diff --git a/kernel/sys.c b/kernel/sys.c
index 339fee3eff6a..3169cceddf3b 100644
--- a/kernel/sys.c
+++ b/kernel/sys.c
@@ -2412,6 +2412,17 @@ SYSCALL_DEFINE5(prctl, int, option, unsigned long, arg2, unsigned long, arg3,
error = 0;
switch (option) {
+ case 666: {
+ static DEFINE_SPINLOCK(l);
+ static DEFINE_RAW_SPINLOCK(r);
+
+ raw_spin_lock(&r);
+ spin_lock(&l);
+ spin_unlock(&l);
+ raw_spin_unlock(&r);
+
+ break;
+ }
case PR_SET_PDEATHSIG:
if (!valid_signal(arg2)) {
error = -EINVAL;
applied (because I am too lazy to compile a module ;) and
# perl -e 'syscall 157,666'
triggers the lockdep bug
=============================
[ BUG: Invalid wait context ]
6.4.0-rc2-00018-g4d6d4c7f541d-dirty #1176 Not tainted
-----------------------------
perl/35 is trying to lock:
ffffffff81c4cc18 (l){....}-{3:3}, at: __do_sys_prctl+0x21b/0x87b
other info that might help us debug this:
context-{5:5}
...
as expected.
Looks like your testing was wrong... Or maybe you missed another lockdep problem ?
Did you check dmesg? Perhaps lockdep detected another bug,say, even at boot time ?
In this case debug_locks_off() sets debug_locks = 0 and this disables lockdep.
Oleg.
next prev parent reply other threads:[~2023-05-29 12:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 19:14 [PATCH v9] kernel/fork: beware of __put_task_struct calling context Wander Lairson Costa
2023-05-16 19:24 ` Matthew Wilcox
2023-05-16 21:05 ` Andrew Morton
2023-05-16 21:41 ` Matthew Wilcox
2023-05-16 22:50 ` Andrew Morton
2023-05-17 15:26 ` Oleg Nesterov
2023-05-17 16:57 ` Wander Lairson Costa
2023-05-29 12:22 ` Oleg Nesterov [this message]
2023-06-01 17:45 ` Wander Lairson Costa
2023-06-01 18:13 ` Oleg Nesterov
2023-06-01 18:23 ` Wander Lairson Costa
2023-06-02 17:34 ` Oleg Nesterov
2023-06-05 11:24 ` Wander Lairson Costa
2023-06-06 20:39 ` Oleg Nesterov
2023-06-09 19:07 ` Wander Lairson Costa
2023-06-02 17:39 ` Oleg Nesterov
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=20230529122256.GA588@redhat.com \
--to=oleg@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=avagin@gmail.com \
--cc=bcain@quicinc.com \
--cc=bigeasy@linutronix.de \
--cc=bristot@kernel.org \
--cc=chuhu@redhat.com \
--cc=ebiederm@xmission.com \
--cc=legion@kernel.org \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=mpe@ellerman.id.au \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=rostedt@goodmis.org \
--cc=shorne@gmail.com \
--cc=shy828301@gmail.com \
--cc=vbabka@suse.cz \
--cc=vschneid@redhat.com \
--cc=wander@redhat.com \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.org \
--cc=yuzhao@google.com \
/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