From: Josh Poimboeuf <jpoimboe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Linus Torvalds
<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: kernel test robot
<fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
LKP <lkp-JC7UmRfGjtg@public.gmane.org>,
linux-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
dma <dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
USB list <linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Vinod Koul <vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
wfg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org
Subject: Re: 4879b7ae05 ("Merge tag 'dmaengine-4.12-rc1' of .."): WARNING: kernel stack regs at bd92bc2e in 01-cpu-hotplug:3811 has bad 'bp' value 000001be
Date: Mon, 2 Oct 2017 16:26:54 -0500 [thread overview]
Message-ID: <20171002212654.rsm4uj3hfioddldd@treble> (raw)
In-Reply-To: <CA+55aFz_ijfUxyk2kdLhfzfS1z0_uRBw6eQb9UxFvh=5zOzzaw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Mon, Oct 02, 2017 at 01:09:31PM -0700, Linus Torvalds wrote:
> Bringing in Josh on this, because the merge commit gets fingered
> because it seems to be an interaction between the new code from the
> merge and the ORC unwinder changes. It's probably some almost trivial
> code difference that just causes some code generation to change.
>
> And because Josh wasn't implicated in the merge, he didn't get cc'd by
> the kernel test robot.
>
> Of course, the stack trace itself seems to be pretty useless, since
> that randconfig doesn't have KALLSYMS enabled, so it's just random hex
> numbers.
>
> Josh, original email on lkml and a few other mailing lists, see for example:
>
> https://www.spinics.net/lists/devicetree/msg196692.html
>
> Any ideas?
The bisect is pointing to a commit which is almost 5 months old, so this
is pre-ORC. Kallsyms *is* enabled, but the unwinder dump isn't smart
enough to realize it's dumping misaligned stack addresses:
[ 110.399425] WARNING: kernel stack regs at bd92bc2e in 01-cpu-hotplug:3811 has bad 'bp' value 000001be
[ 110.399428] unwind stack type:0 next_sp: (null) mask:0x2 graph_idx:0
[ 110.399431] bd92bc2e: 92bc7f00 (0x92bc7f00)
[ 110.399433] bd92bc32: c27041bd (0xc27041bd)
So kallsyms doesn't help if I'm dumping bad data. Oops.
I tried to recreate it with the reproducer script and a similar GCC
version, but no luck.
Fengguang, assuming it's reliably recreatable, any chance you could
recreate with the following patch?
diff --git a/arch/x86/kernel/unwind_frame.c b/arch/x86/kernel/unwind_frame.c
index 82c6d7f1fd73..64282ec73eb8 100644
--- a/arch/x86/kernel/unwind_frame.c
+++ b/arch/x86/kernel/unwind_frame.c
@@ -42,7 +42,7 @@ 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); sp; sp = PTR_ALIGN(stack_info.next_sp, sizeof(long))) {
if (get_stack_info(sp, state->task, &stack_info, &visit_mask))
break;
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Josh Poimboeuf <jpoimboe@redhat.com>
To: lkp@lists.01.org
Subject: Re: 4879b7ae05 ("Merge tag 'dmaengine-4.12-rc1' of .."): WARNING: kernel stack regs at bd92bc2e in 01-cpu-hotplug:3811 has bad 'bp' value 000001be
Date: Mon, 02 Oct 2017 16:26:54 -0500 [thread overview]
Message-ID: <20171002212654.rsm4uj3hfioddldd@treble> (raw)
In-Reply-To: <CA+55aFz_ijfUxyk2kdLhfzfS1z0_uRBw6eQb9UxFvh=5zOzzaw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2160 bytes --]
On Mon, Oct 02, 2017 at 01:09:31PM -0700, Linus Torvalds wrote:
> Bringing in Josh on this, because the merge commit gets fingered
> because it seems to be an interaction between the new code from the
> merge and the ORC unwinder changes. It's probably some almost trivial
> code difference that just causes some code generation to change.
>
> And because Josh wasn't implicated in the merge, he didn't get cc'd by
> the kernel test robot.
>
> Of course, the stack trace itself seems to be pretty useless, since
> that randconfig doesn't have KALLSYMS enabled, so it's just random hex
> numbers.
>
> Josh, original email on lkml and a few other mailing lists, see for example:
>
> https://www.spinics.net/lists/devicetree/msg196692.html
>
> Any ideas?
The bisect is pointing to a commit which is almost 5 months old, so this
is pre-ORC. Kallsyms *is* enabled, but the unwinder dump isn't smart
enough to realize it's dumping misaligned stack addresses:
[ 110.399425] WARNING: kernel stack regs at bd92bc2e in 01-cpu-hotplug:3811 has bad 'bp' value 000001be
[ 110.399428] unwind stack type:0 next_sp: (null) mask:0x2 graph_idx:0
[ 110.399431] bd92bc2e: 92bc7f00 (0x92bc7f00)
[ 110.399433] bd92bc32: c27041bd (0xc27041bd)
So kallsyms doesn't help if I'm dumping bad data. Oops.
I tried to recreate it with the reproducer script and a similar GCC
version, but no luck.
Fengguang, assuming it's reliably recreatable, any chance you could
recreate with the following patch?
diff --git a/arch/x86/kernel/unwind_frame.c b/arch/x86/kernel/unwind_frame.c
index 82c6d7f1fd73..64282ec73eb8 100644
--- a/arch/x86/kernel/unwind_frame.c
+++ b/arch/x86/kernel/unwind_frame.c
@@ -42,7 +42,7 @@ 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); sp; sp = PTR_ALIGN(stack_info.next_sp, sizeof(long))) {
if (get_stack_info(sp, state->task, &stack_info, &visit_mask))
break;
WARNING: multiple messages have this Message-ID (diff)
From: jpoimboe@redhat.com (Josh Poimboeuf)
To: linux-arm-kernel@lists.infradead.org
Subject: 4879b7ae05 ("Merge tag 'dmaengine-4.12-rc1' of .."): WARNING: kernel stack regs at bd92bc2e in 01-cpu-hotplug:3811 has bad 'bp' value 000001be
Date: Mon, 2 Oct 2017 16:26:54 -0500 [thread overview]
Message-ID: <20171002212654.rsm4uj3hfioddldd@treble> (raw)
In-Reply-To: <CA+55aFz_ijfUxyk2kdLhfzfS1z0_uRBw6eQb9UxFvh=5zOzzaw@mail.gmail.com>
On Mon, Oct 02, 2017 at 01:09:31PM -0700, Linus Torvalds wrote:
> Bringing in Josh on this, because the merge commit gets fingered
> because it seems to be an interaction between the new code from the
> merge and the ORC unwinder changes. It's probably some almost trivial
> code difference that just causes some code generation to change.
>
> And because Josh wasn't implicated in the merge, he didn't get cc'd by
> the kernel test robot.
>
> Of course, the stack trace itself seems to be pretty useless, since
> that randconfig doesn't have KALLSYMS enabled, so it's just random hex
> numbers.
>
> Josh, original email on lkml and a few other mailing lists, see for example:
>
> https://www.spinics.net/lists/devicetree/msg196692.html
>
> Any ideas?
The bisect is pointing to a commit which is almost 5 months old, so this
is pre-ORC. Kallsyms *is* enabled, but the unwinder dump isn't smart
enough to realize it's dumping misaligned stack addresses:
[ 110.399425] WARNING: kernel stack regs at bd92bc2e in 01-cpu-hotplug:3811 has bad 'bp' value 000001be
[ 110.399428] unwind stack type:0 next_sp: (null) mask:0x2 graph_idx:0
[ 110.399431] bd92bc2e: 92bc7f00 (0x92bc7f00)
[ 110.399433] bd92bc32: c27041bd (0xc27041bd)
So kallsyms doesn't help if I'm dumping bad data. Oops.
I tried to recreate it with the reproducer script and a similar GCC
version, but no luck.
Fengguang, assuming it's reliably recreatable, any chance you could
recreate with the following patch?
diff --git a/arch/x86/kernel/unwind_frame.c b/arch/x86/kernel/unwind_frame.c
index 82c6d7f1fd73..64282ec73eb8 100644
--- a/arch/x86/kernel/unwind_frame.c
+++ b/arch/x86/kernel/unwind_frame.c
@@ -42,7 +42,7 @@ 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); sp; sp = PTR_ALIGN(stack_info.next_sp, sizeof(long))) {
if (get_stack_info(sp, state->task, &stack_info, &visit_mask))
break;
WARNING: multiple messages have this Message-ID (diff)
From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: kernel test robot <fengguang.wu@intel.com>, LKP <lkp@01.org>,
linux-soc@vger.kernel.org, linux-arm-msm@vger.kernel.org,
dma <dmaengine@vger.kernel.org>,
linux-samsung-soc@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
Vinod Koul <vinod.koul@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
wfg@linux.intel.com
Subject: Re: 4879b7ae05 ("Merge tag 'dmaengine-4.12-rc1' of .."): WARNING: kernel stack regs at bd92bc2e in 01-cpu-hotplug:3811 has bad 'bp' value 000001be
Date: Mon, 2 Oct 2017 16:26:54 -0500 [thread overview]
Message-ID: <20171002212654.rsm4uj3hfioddldd@treble> (raw)
In-Reply-To: <CA+55aFz_ijfUxyk2kdLhfzfS1z0_uRBw6eQb9UxFvh=5zOzzaw@mail.gmail.com>
On Mon, Oct 02, 2017 at 01:09:31PM -0700, Linus Torvalds wrote:
> Bringing in Josh on this, because the merge commit gets fingered
> because it seems to be an interaction between the new code from the
> merge and the ORC unwinder changes. It's probably some almost trivial
> code difference that just causes some code generation to change.
>
> And because Josh wasn't implicated in the merge, he didn't get cc'd by
> the kernel test robot.
>
> Of course, the stack trace itself seems to be pretty useless, since
> that randconfig doesn't have KALLSYMS enabled, so it's just random hex
> numbers.
>
> Josh, original email on lkml and a few other mailing lists, see for example:
>
> https://www.spinics.net/lists/devicetree/msg196692.html
>
> Any ideas?
The bisect is pointing to a commit which is almost 5 months old, so this
is pre-ORC. Kallsyms *is* enabled, but the unwinder dump isn't smart
enough to realize it's dumping misaligned stack addresses:
[ 110.399425] WARNING: kernel stack regs at bd92bc2e in 01-cpu-hotplug:3811 has bad 'bp' value 000001be
[ 110.399428] unwind stack type:0 next_sp: (null) mask:0x2 graph_idx:0
[ 110.399431] bd92bc2e: 92bc7f00 (0x92bc7f00)
[ 110.399433] bd92bc32: c27041bd (0xc27041bd)
So kallsyms doesn't help if I'm dumping bad data. Oops.
I tried to recreate it with the reproducer script and a similar GCC
version, but no luck.
Fengguang, assuming it's reliably recreatable, any chance you could
recreate with the following patch?
diff --git a/arch/x86/kernel/unwind_frame.c b/arch/x86/kernel/unwind_frame.c
index 82c6d7f1fd73..64282ec73eb8 100644
--- a/arch/x86/kernel/unwind_frame.c
+++ b/arch/x86/kernel/unwind_frame.c
@@ -42,7 +42,7 @@ 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); sp; sp = PTR_ALIGN(stack_info.next_sp, sizeof(long))) {
if (get_stack_info(sp, state->task, &stack_info, &visit_mask))
break;
next prev parent reply other threads:[~2017-10-02 21:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-01 23:17 4879b7ae05 ("Merge tag 'dmaengine-4.12-rc1' of .."): WARNING: kernel stack regs at bd92bc2e in 01-cpu-hotplug:3811 has bad 'bp' value 000001be kernel test robot
2017-10-01 23:17 ` kernel test robot
2017-10-01 23:17 ` kernel test robot
2017-10-02 20:09 ` Linus Torvalds
2017-10-02 20:09 ` Linus Torvalds
2017-10-02 20:09 ` Linus Torvalds
[not found] ` <CA+55aFz_ijfUxyk2kdLhfzfS1z0_uRBw6eQb9UxFvh=5zOzzaw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-02 21:26 ` Josh Poimboeuf [this message]
2017-10-02 21:26 ` Josh Poimboeuf
2017-10-02 21:26 ` Josh Poimboeuf
2017-10-02 21:26 ` Josh Poimboeuf
2017-10-02 21:31 ` Josh Poimboeuf
2017-10-02 21:31 ` Josh Poimboeuf
2017-10-02 21:31 ` Josh Poimboeuf
2017-10-03 3:45 ` Fengguang Wu
2017-10-03 3:45 ` Fengguang Wu
2017-10-03 3:45 ` Fengguang Wu
2017-10-03 13:21 ` Josh Poimboeuf
2017-10-03 13:21 ` Josh Poimboeuf
2017-10-03 13:21 ` Josh Poimboeuf
2017-10-03 13:45 ` Fengguang Wu
2017-10-03 13:45 ` Fengguang Wu
2017-10-03 13:45 ` Fengguang Wu
2017-10-03 13:45 ` Fengguang Wu
2017-10-02 21:58 ` Linus Torvalds
2017-10-02 21:58 ` Linus Torvalds
2017-10-02 21:58 ` Linus Torvalds
2017-10-03 1:17 ` Josh Poimboeuf
2017-10-03 1:17 ` Josh Poimboeuf
2017-10-03 1:17 ` 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=20171002212654.rsm4uj3hfioddldd@treble \
--to=jpoimboe-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lkp-JC7UmRfGjtg@public.gmane.org \
--cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=wfg-VuQAYsv1563Yd54FQh9/CA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.