From: "Paul E. McKenney" <paulmck@kernel.org>
To: Sachin Sant <sachinp@linux.ibm.com>
Cc: Zqiang <qiang1.zhang@intel.com>,
linux-next@vger.kernel.org,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [next-20230322] Kernel WARN at kernel/workqueue.c:3182 (rcutorture)
Date: Thu, 23 Mar 2023 20:32:40 -0700 [thread overview]
Message-ID: <bed6b499-76cc-4412-8a4d-c71f03276726@paulmck-laptop> (raw)
In-Reply-To: <23F7ADE0-0B96-4257-8910-6B678E0F0C7A@linux.ibm.com>
On Fri, Mar 24, 2023 at 08:47:38AM +0530, Sachin Sant wrote:
>
> >>> 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?
> >>
> >> Thank you for the patch. Yes, with this patch applied, the test completes
> >> successfully without the reported warning.
> >
> > Very good, thank you! May we have your Tested-by?
>
> Tested-by: Sachin Sant <sachinp@linux.ibm.com>
Thank you, and I will apply on the next rebase.
Thanx, Paul
prev parent reply other threads:[~2023-03-24 3:33 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
2023-03-23 18:34 ` Paul E. McKenney
2023-03-24 3:17 ` Sachin Sant
2023-03-24 3:32 ` Paul E. McKenney [this message]
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=bed6b499-76cc-4412-8a4d-c71f03276726@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=qiang1.zhang@intel.com \
--cc=sachinp@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).