From: Paul Menzel <pmenzel@molgen.mpg.de>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org, linux-mm@kvack.org,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Jason Baron <jbaron@akamai.com>,
rcu@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Zhouyi Zhou <zhouzhouyi@gmail.com>
Subject: Re: BUG: sleeping function called from invalid context at include/linux/sched/mm.h:256
Date: Sun, 13 Feb 2022 18:26:53 +0100 [thread overview]
Message-ID: <18464474-77e9-1a53-265f-b9718d43e8cd@molgen.mpg.de> (raw)
In-Reply-To: <20220213144542.GT4285@paulmck-ThinkPad-P17-Gen-1>
Dear Paul,
Am 13.02.22 um 15:45 schrieb Paul E. McKenney:
> On Sun, Feb 13, 2022 at 08:39:13AM +0100, Paul Menzel wrote:
>> Am 13.02.22 um 00:48 schrieb Paul E. McKenney:
>>> On Sun, Feb 13, 2022 at 12:05:50AM +0100, Paul Menzel wrote:
>>
>> […]
>>
>>>> Running rcutorture on the POWER8 system IBM S822LC with Ubuntu 20.10, it
>>>> found the bug below. I more or less used rcu/dev (0ba8896d2fd7
>>>> (lib/irq_poll: Declare IRQ_POLL softirq vector as ksoftirqd-parking safe))
>>>> [1]. The bug manifested for the four configurations below.
>>>>
>>>> 1. results-rcutorture-kasan/SRCU-T
>>>> 2. results-rcutorture-kasan/TINY02
>>>> 3. results-rcutorture/SRCU-T
>>>> 4. results-rcutorture/TINY02
>>>
>>> Adding Frederic on CC...
>>>
>>> I am dropping these three for the moment:
>>>
>>> 0ba8896d2fd75 lib/irq_poll: Declare IRQ_POLL softirq vector as ksoftirqd-parking safe
>>> efa8027149a1f tick/rcu: Stop allowing RCU_SOFTIRQ in idle
>>> d338d22b9d338 tick/rcu: Remove obsolete rcu_needs_cpu() parameters
>>>
>>> Though it might be that these are victims of circumstance, in other
>>> words, that the original bug that Paul Menzel reported was caused by
>>> something else.
>>
>> Even without these three patches, the issue is reproducible. I tested commit
>> 7a935b7ac61b (tools/nolibc/stdlib: implement abort()).
>
> Ah, I thought you were saying that the issue was caused by them.
>
> I will put them back. And apologies to Frederic for kicking his
> patches out!
Sorry for being unclear.
> Are you able to bisect to see what commit introduced the problem?
I have not checked yet, if it’s a regression. I am going to test it next
week.
[…]
Kind regards,
next prev parent reply other threads:[~2022-02-13 17:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 23:05 Paul Menzel
2022-02-12 23:48 ` Paul E. McKenney
2022-02-13 7:39 ` Paul Menzel
2022-02-13 14:45 ` Paul E. McKenney
2022-02-13 17:26 ` Paul Menzel [this message]
2022-02-13 3:19 ` Zhouyi Zhou
2022-02-13 4:09 ` Matthew Wilcox
2022-02-13 4:17 ` Zhouyi Zhou
2022-02-14 9:35 ` Peter Zijlstra
2022-02-14 9:50 ` Christophe Leroy
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=18464474-77e9-1a53-265f-b9718d43e8cd@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=jbaron@akamai.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=zhouzhouyi@gmail.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