From: Oliver Sang <oliver.sang@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: lkp@lists.01.org, lkp@intel.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [rcu] 758cf1496b: BUG:spinlock_bad_magic_on_CPU
Date: Thu, 17 Mar 2022 08:45:56 +0800 [thread overview]
Message-ID: <20220317004556.GA32394@xsang-OptiPlex-9020> (raw)
In-Reply-To: <20220316170437.GJ4285@paulmck-ThinkPad-P17-Gen-1>
hi Paul,
On Wed, Mar 16, 2022 at 10:04:37AM -0700, Paul E. McKenney wrote:
> On Wed, Mar 16, 2022 at 02:16:28PM +0800, Oliver Sang wrote:
> > hi, Paul,
> >
> > On Mon, Mar 14, 2022 at 07:06:53AM -0700, Paul E. McKenney wrote:
> > > On Mon, Mar 14, 2022 at 01:50:57PM +0800, kernel test robot wrote:
> > > >
> > > >
> > > > Greeting,
> > > >
> > > > FYI, we noticed the following commit (built with gcc-9):
> > > >
> > > > commit: 758cf1496b94442c47c339b10d80cbaadf613425 ("rcu: Make UP-vacuous normal grace period advance sequence")
> > > > https://github.com/ammarfaizi2/linux-block paulmck/linux-rcu/dev.2022.03.09a
> > > >
> > > > in testcase: boot
> > > >
> > > > on test machine: qemu-system-x86_64 -enable-kvm -cpu Icelake-Server -smp 4 -m 16G
> > > >
> > > > caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
> > > >
> > > >
> > > > +--------------------------------------+------------+------------+
> > > > | | 6129c2b2dc | 758cf1496b |
> > > > +--------------------------------------+------------+------------+
> > > > | BUG:spinlock_bad_magic_on_CPU | 0 | 16 |
> > > > | WARNING:at_init/main.c:#start_kernel | 0 | 16 |
> > > > | RIP:start_kernel | 0 | 16 |
> > > > +--------------------------------------+------------+------------+
> > > >
> > > >
> > > > If you fix the issue, kindly add following tag
> > > > Reported-by: kernel test robot <oliver.sang@intel.com>
> > >
> > > Does this fix it for you?
> > >
> > > 67792d475181 ("fixup! rcu: Make UP-vacuous normal grace period advance sequence")
> >
> > yes, this fixed:
> >
> > 6129c2b2dc65abde 758cf1496b94442c47c339b10d8 67792d4751810a675c5690ce2e9
> > ---------------- --------------------------- ---------------------------
> > fail:runs %reproduction fail:runs %reproduction fail:runs
> > | | | | |
> > :6 100% 6:6 0% :20 dmesg.BUG:spinlock_bad_magic_on_CPU
> > :6 100% 6:6 0% :20 dmesg.RIP:start_kernel
> > :6 100% 6:6 0% :20 dmesg.WARNING:at_init/main.c:#start_kernel
>
> Very good, thank you!
>
> May I add your Tested-by?
sure! our great pleasure :)
Tested-by: kernel test robot <oliver.sang@intel.com>
>
> Thanx, Paul
>
prev parent reply other threads:[~2022-03-17 0:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 5:50 kernel test robot
2022-03-14 14:06 ` Paul E. McKenney
2022-03-16 6:16 ` Oliver Sang
2022-03-16 17:04 ` Paul E. McKenney
2022-03-17 0:45 ` Oliver Sang [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=20220317004556.GA32394@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=paulmck@kernel.org \
/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
all inboxes | Powered by JetHome®