Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain;
        charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\))
Subject: Re: [next-20230322] Kernel WARN at kernel/workqueue.c:3182
 (rcutorture)
From:   Sachin Sant <sachinp@linux.ibm.com>
In-Reply-To: <fbb628c1-08bd-44ff-a613-794b134f6d46@paulmck-laptop>
Date:   Thu, 23 Mar 2023 23:00:59 +0530
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>
Content-Transfer-Encoding: quoted-printable
Message-Id: <233B28DA-70DD-4AD8-9C72-1FFCA6EFE56D@linux.ibm.com>
References: <139BEB3F-BC1C-4ABA-8928-9A8EF3FB5EDD@linux.ibm.com>
 <fbb628c1-08bd-44ff-a613-794b134f6d46@paulmck-laptop>
To:     "Paul E. McKenney" <paulmck@kernel.org>
Precedence: bulk


>> [ 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=20
>> [ 3629.243430] ---[ end trace 0000000000000000 ]=E2=80=94
>>=20
>> These warnings are repeated few times. The LTP test is marked as =
PASS.
>>=20
>> Git bisect point to the following patch
>> commit f46a5170e6e7d5f836f2199fe82cdb0b4363427f
>>    srcu: Use static init for statically allocated in-module =
srcu_struct
>=20
> 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.
>=20
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?
>=20
> Thanx, Paul
>=20

Thank you for the patch. Yes, with this patch applied, the test =
completes
successfully without the reported warning.

- Sachin