From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Daniel J Blueman <daniel@quora.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: stack frame unwindind KASAN errors
Date: Mon, 6 Mar 2017 10:40:08 -0600 [thread overview]
Message-ID: <20170306164008.dgg3xthl2ihsdfnu@treble> (raw)
In-Reply-To: <CAMVG2svLNL2=kA-bzFBoCunm60+av0x-3Dfx1C1dUGEDyOJHhQ@mail.gmail.com>
On Mon, Mar 06, 2017 at 02:52:01PM +0800, Daniel J Blueman wrote:
> Thanks Josh!
>
> With this patch, the KASAN warning still occurs, but at
> unwind_get_return_address+0x1d3/0x130 instead; the rest of the trace
> is identical.
>
> (gdb) list *(unwind_get_return_address+0x1d3)
> 0xffffffff8112bca3 is in unwind_get_return_address
> (./include/linux/compiler.h:243).
> 238 })
> 239
> 240 static __always_inline
> 241 void __read_once_size(const volatile void *p, void *res, int size)
> 242 {
> 243 __READ_ONCE_SIZE;
Looking deeper, I have an idea about what's going on:
https://quora.org/dmesg.txt
Each of the warnings seems to show an interrupt happening during an EFI
call. I'm guessing EFI modified the frame pointer, at least
temporarily, which confused the unwinder :-(
Would it be possible for you to test again with 4.10? It has some
additional unwinder output which should hopefully confirm my suspicions.
--
Josh
next prev parent reply other threads:[~2017-03-06 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 4:49 Daniel J Blueman
2017-02-27 15:47 ` Josh Poimboeuf
2017-03-06 6:52 ` Daniel J Blueman
2017-03-06 16:40 ` Josh Poimboeuf [this message]
2017-03-07 2:04 ` Daniel J Blueman
2017-03-07 14:32 ` 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=20170306164008.dgg3xthl2ihsdfnu@treble \
--to=jpoimboe@redhat.com \
--cc=daniel@quora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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®