From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>, Andy Lutomirski <luto@kernel.org>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
Borislav Petkov <bp@alien8.de>
Subject: Re: WARNING: Kernel stack regs has bad 'bp' value
Date: Fri, 11 Sep 2020 12:09:11 -0500 [thread overview]
Message-ID: <20200911170911.mrkorgsplrrwp4rv@treble> (raw)
In-Reply-To: <5a66f512-960b-7f24-068a-01c043ca9877@deltatee.com>
On Fri, Sep 11, 2020 at 10:14:41AM -0600, Logan Gunthorpe wrote:
>
>
> On 2020-09-11 10:00 a.m., Josh Poimboeuf wrote:
> > Hi Logan,
> >
> > Thanks for the bug report. (Sorry I missed the first one, Naresh.)
> >
> > The problem is that ret_from_fork() is no longer in .entry.text, so the
> > following check in the FP unwinder doesn't work when ret_from_fork()
> > gets interrupted.
> >
> > /*
> > * Don't warn if the unwinder got lost due to an interrupt in entry
> > * code or in the C handler before the first frame pointer got set up:
> > */
> > if (state->got_irq && in_entry_code(state->ip))
> > goto the_end;
> >
> > If you have the ability to recreate, can you try the following patch?
>
> Sorry, but I can not reliably hit this bug. I hit it randomly twice last
> week however, despite doing a bunch more runs this week, I haven't hit
> it again.
>
> I can add the patch to my testing next week but I ca not give you a
> definitive answer on whether this fixes the bug.
>
> Perhaps Naresh's test is a better reproducer.
That's ok. I forced a reproducer by putting an infinite loop in
ret_from_fork to force an APIC interrupt with lockdep unwind.
The patch fixes it, I'll post an official version after some more
testing.
--
Josh
next prev parent reply other threads:[~2020-09-11 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 19:42 WARNING: Kernel stack regs has bad 'bp' value Logan Gunthorpe
2020-09-11 16:00 ` Josh Poimboeuf
2020-09-11 16:14 ` Logan Gunthorpe
2020-09-11 17:09 ` Josh Poimboeuf [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-23 3:34 WARNING: kernel stack regs has bad "bp" value wzs
2024-12-23 14:11 ` Josh Poimboeuf
2024-12-24 3:17 ` wzs
2024-12-24 6:51 ` Josh Poimboeuf
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=20200911170911.mrkorgsplrrwp4rv@treble \
--to=jpoimboe@redhat.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=tglx@linutronix.de \
--cc=x86@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