From: Neeraj Upadhyay <Neeraj.Upadhyay@kernel.org>
To: Oliver Sang <oliver.sang@intel.com>
Cc: Frederic Weisbecker <frederic@kernel.org>,
Joel Fernandes <joelagnelf@nvidia.com>,
oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org,
Xiongfeng Wang <wangxiongfeng2@huawei.com>,
Qi Xi <xiqi2@huawei.com>, "Paul E. McKenney" <paulmck@kernel.org>,
Linux Kernel Functional Testing <lkft@linaro.org>,
rcu@vger.kernel.org
Subject: Re: [linus:master] [rcu] b41642c877: BUG:kernel_hang_in_boot_stage
Date: Wed, 13 Aug 2025 19:25:49 +0530 [thread overview]
Message-ID: <20250813135549.GA3156@neeraj.linux> (raw)
In-Reply-To: <aJyWmUdR0LzIiSai@xsang-OptiPlex-9020>
On Wed, Aug 13, 2025 at 09:43:53PM +0800, Oliver Sang wrote:
> hi, Neeraj,
>
> On Wed, Aug 13, 2025 at 10:10:24AM +0530, Neeraj Upadhyay wrote:
> > Hi kernel test robot,
> >
> > > #syz test
>
> sorry, we are not syz bot :) didn't capture this.
>
Ah ok!
> [...]
>
> > > Fixes: b41642c87716 ("rcu: Fix rcu_read_unlock() deadloop due to IRQ work")
> > > Reported-by: kernel test robot <oliver.sang@intel.com>
> > > Closes: https://lore.kernel.org/oe-lkp/202508071303.c1134cce-lkp@intel.com
> > > Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
> > > ---
> >
> > Can you please update testing results with the proposed fix?
>
> now we finished the test with the proposed fix, it works. thanks!
>
> Tested-by: kernel test robot <oliver.sang@intel.com>
>
Thanks for testing!
- Neeraj
> >
> >
> > - Neeraj
> >
prev parent reply other threads:[~2025-08-13 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 5:39 [linus:master] [rcu] b41642c877: BUG:kernel_hang_in_boot_stage kernel test robot
2025-08-08 17:34 ` Frederic Weisbecker
2025-08-09 19:02 ` Joel Fernandes
2025-08-13 4:40 ` Neeraj Upadhyay
2025-08-13 13:43 ` Oliver Sang
2025-08-13 13:55 ` Neeraj Upadhyay [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=20250813135549.GA3156@neeraj.linux \
--to=neeraj.upadhyay@kernel.org \
--cc=frederic@kernel.org \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft@linaro.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=wangxiongfeng2@huawei.com \
--cc=xiqi2@huawei.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).