mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: bp@alien8.de, 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 inswapper:1 has bad 'bp' value 0ba00000
Date: Tue, 3 Oct 2017 09:35:18 -0500	[thread overview]
Message-ID: <20171003143518.xgw7ifylwjhi25xx@treble> (raw)
In-Reply-To: <201710032244.ADC26527.FStOFOJOFLMVHQ@I-love.SAKURA.ne.jp>

On Tue, Oct 03, 2017 at 10:44:13PM +0900, Tetsuo Handa wrote:
> Josh Poimboeuf wrote:
> 
> > 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.
> > 
> I see. Here is the result.

Hm, that's not what I expected to happen...  I suspect this is stack
corruption, with the result being slightly different every time.  Can
you see if this patch fixes the panic?


diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c
index 44c8d0d17170..b4a5e60488aa 100644
--- a/kernel/locking/lockdep.c
+++ b/kernel/locking/lockdep.c
@@ -1986,7 +1986,7 @@ check_prevs_add(struct task_struct *curr, struct held_lock *next)
 {
 	int depth = curr->lockdep_depth;
 	struct held_lock *hlock;
-	struct stack_trace trace;
+	static struct stack_trace trace;
 	int (*save)(struct stack_trace *trace) = save_trace;
 
 	/*

  reply	other threads:[~2017-10-03 14:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-08 13:06 [4.14-rc1 x86] WARNING: kernel stack regs at f60bbb12 in swapper:1 " 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
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 [this message]
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=20171003143518.xgw7ifylwjhi25xx@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®