[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <bed6b499-76cc-4412-8a4d-c71f03276726@paulmck-laptop>
Date: Thu, 23 Mar 2023 20:32:40 -0700
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Sachin Sant <sachinp@...ux.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
linux-next@...r.kernel.org,
open list <linux-kernel@...r.kernel.org>,
Zqiang <qiang1.zhang@...el.com>
Subject: Re: [next-20230322] Kernel WARN at kernel/workqueue.c:3182
(rcutorture)
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@...ux.ibm.com>
Thank you, and I will apply on the next rebase.
Thanx, Paul
Powered by blists - more mailing lists