From: Sachin Sant <sachinp@linux•ibm.com>
To: "Paul E. McKenney" <paulmck@kernel•org>
Cc: linuxppc-dev <linuxppc-dev@lists•ozlabs.org>,
linux-next@vger•kernel.org,
open list <linux-kernel@vger•kernel.org>,
Zqiang <qiang1.zhang@intel•com>
Subject: Re: [next-20230322] Kernel WARN at kernel/workqueue.c:3182 (rcutorture)
Date: Thu, 23 Mar 2023 23:00:59 +0530 [thread overview]
Message-ID: <233B28DA-70DD-4AD8-9C72-1FFCA6EFE56D@linux.ibm.com> (raw)
In-Reply-To: <fbb628c1-08bd-44ff-a613-794b134f6d46@paulmck-laptop>
>> [ 3629.243407] NIP [00007fff8cd39558] 0x7fff8cd39558
>> [ 3629.243410] LR [000000010d800398] 0x10d800398
>> [ 3629.243413] --- interrupt: c00
>> [ 3629.243415] Code: 419dffa4 e93a0078 39400001 552907be 2f890000 7d20579e 0b090000 e95a0078 e91a0080 39200001 7fa85000 7d204f9e <0b090000> 7f23cb78 4bfffd65 0b030000
>> [ 3629.243430] ---[ end trace 0000000000000000 ]—
>>
>> These warnings are repeated few times. The LTP test is marked as PASS.
>>
>> Git bisect point to the following patch
>> commit f46a5170e6e7d5f836f2199fe82cdb0b4363427f
>> srcu: Use static init for statically allocated in-module srcu_struct
>
> Hello, Sachin, and it looks like you hit something that Zqiang and I
> have been tracking down. I am guessing that you were using modprobe
> and rmmod to make this happen, and that this happened at rmmod time.
>
Yes, the LTP test script rcu_torture.sh relies on modprobe to load/unload
the rcutorture module.
> Whatever the reproducer, does the following patch help?
>
> Thanx, Paul
>
Thank you for the patch. Yes, with this patch applied, the test completes
successfully without the reported warning.
- Sachin
next prev parent reply other threads:[~2023-03-23 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 11:25 [next-20230322] Kernel WARN at kernel/workqueue.c:3182 (rcutorture) Sachin Sant
2023-03-23 14:02 ` Paul E. McKenney
2023-03-23 17:30 ` Sachin Sant [this message]
2023-03-23 18:34 ` Paul E. McKenney
2023-03-24 3:17 ` Sachin Sant
2023-03-24 3:32 ` Paul E. McKenney
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=233B28DA-70DD-4AD8-9C72-1FFCA6EFE56D@linux.ibm.com \
--to=sachinp@linux$(echo .)ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=paulmck@kernel$(echo .)org \
--cc=qiang1.zhang@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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