From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: [4.14-rc1 x86] WARNING: kernel stack regs at f60bbb12 in swapper:1 has bad 'bp' value 0ba00000
Date: Tue, 3 Oct 2017 08:29:15 -0500 [thread overview]
Message-ID: <20171003132915.poy7sv73eev6to7m@treble> (raw)
In-Reply-To: <20171003103744.hxnz7o73rxzj63gx@pd.tnic>
On Tue, Oct 03, 2017 at 12:37:44PM +0200, Borislav Petkov wrote:
> On Tue, Oct 03, 2017 at 07:29:36PM +0900, Tetsuo Handa wrote:
> > Tetsuo Handa wrote:
> > > Tetsuo Handa wrote:
> > > > Tetsuo Handa wrote:
> > > > > I'm seeing below error between
> > > > > 4898b99c261efe32 ("Merge tag 'acpi-4.13-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm") (git bisect good (presumably))
> > > > > e6f3faa734a00c60 ("locking/lockdep: Fix workqueue crossrelease annotation") (git bisect bad) on linux.git .
> > > >
> > > > F.Y.I. This error remains as of 46c1e79fee417f15 ("Merge branch 'perf-urgent-for-linus' of
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip") on linux.git .
> > > >
> > >
> > > This error still remains as of 6e80ecdddf4ea6f3 ("Merge branch 'libnvdimm-fixes'
> > > of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm") on linux.git .
> > >
> > > I'm suspecting that this error is causing very unstable x86_32 kernel.
> > > It seems that this error occurs (though rare frequency) even on x86_64 kernel.
> > >
> > > Nobody cares?
> > >
> > 4.14-rc3 still trivially panics due to this error. Is this problem known?
Can you try with the following patch? It should hopefully give more
useful information in the dump.
diff --git a/arch/x86/kernel/unwind_frame.c b/arch/x86/kernel/unwind_frame.c
index d145a0b1f529..191012762aa0 100644
--- a/arch/x86/kernel/unwind_frame.c
+++ b/arch/x86/kernel/unwind_frame.c
@@ -44,7 +44,8 @@ static void unwind_dump(struct unwind_state *state)
state->stack_info.type, state->stack_info.next_sp,
state->stack_mask, state->graph_idx);
- for (sp = state->orig_sp; sp; sp = PTR_ALIGN(stack_info.next_sp, sizeof(long))) {
+ for (sp = PTR_ALIGN(state->orig_sp, sizeof(long)); sp;
+ sp = PTR_ALIGN(stack_info.next_sp, sizeof(long))) {
if (get_stack_info(sp, state->task, &stack_info, &visit_mask))
break;
@@ -178,7 +179,7 @@ static struct pt_regs *decode_frame_pointer(unsigned long *bp)
{
unsigned long regs = (unsigned long)bp;
- if (!(regs & 0x1))
+ if ((regs & (sizeof(long)-1)) != 1)
return NULL;
return (struct pt_regs *)(regs & ~0x1);
@@ -221,6 +222,10 @@ static bool update_stack_state(struct unwind_state *state,
&state->stack_mask))
return false;
+ /* Make sure the frame pointer is properly aligned: */
+ if ((unsigned long)frame & (sizeof(long)-1))
+ return false;
+
/* Make sure it only unwinds up and doesn't overlap the prev frame: */
if (state->orig_sp && state->stack_info.type == prev_type &&
frame < prev_frame_end)
next prev parent reply other threads:[~2017-10-03 13:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 13:06 Tetsuo Handa
[not found] ` <201709142006.GJE87018.QSFJMHOVLOFtOF@I-love.SAKURA.ne.jp>
[not found] ` <201709221335.EDE64522.JSHFFMLFOVOOtQ@I-love.SAKURA.ne.jp>
2017-10-03 10:29 ` Tetsuo Handa
2017-10-03 10:37 ` Borislav Petkov
2017-10-03 13:29 ` Josh Poimboeuf [this message]
2017-10-03 13:44 ` [4.14-rc1 x86] WARNING: kernel stack regs at f60bbb12 inswapper:1 " Tetsuo Handa
2017-10-03 14:35 ` Josh Poimboeuf
2017-10-03 15:09 ` [4.14-rc1 x86] WARNING: kernel stack regs at f60bbb12 in swapper:1 " Tetsuo Handa
2017-10-03 15:15 ` [4.14-rc1 x86] WARNING: kernel stack regs at f60bbb12 inswapper:1 " Josh Poimboeuf
2017-10-03 15:21 ` [4.14-rc1 x86] WARNING: kernel stack regs at f60bbb12 in swapper:1 " Tetsuo Handa
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=20171003132915.poy7sv73eev6to7m@treble \
--to=jpoimboe@redhat.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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
all inboxes | Powered by JetHome®