From: Dmitry Vyukov <dvyukov@google.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: syzbot <syzbot+dac365e3ce07c3d0e496@syzkaller.appspotmail.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [syzbot] WARNING: can't access registers at entry_SYSCALL_64_after_hwframe
Date: Fri, 17 Feb 2023 10:05:52 +0100 [thread overview]
Message-ID: <CACT4Y+aBV3d7kLjAZ1hHHbX=y8gTvfwrPsiohwV81PzRRjGkGQ@mail.gmail.com> (raw)
In-Reply-To: <20230216202607.c2nfp6exhoomjckp@treble>
On Thu, 16 Feb 2023 at 21:26, Josh Poimboeuf <jpoimboe@kernel.org> wrote:
> > > >
> > > > Hello,
> > > >
> > > > syzbot found the following issue on:
> > > >
> > > > HEAD commit: 9d9019bcea1a Add linux-next specific files for 20230215
> > > > git tree: linux-next
> > > > console output: https://syzkaller.appspot.com/x/log.txt?x=144edcc8c80000
> > > > kernel config: https://syzkaller.appspot.com/x/.config?x=a64cbb8ad0da425e
> > > > dashboard link: https://syzkaller.appspot.com/bug?extid=dac365e3ce07c3d0e496
> > > > compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> > > >
> > > > Unfortunately, I don't have any reproducer for this issue yet.
> > > >
> > > > Downloadable assets:
> > > > disk image: https://storage.googleapis.com/syzbot-assets/70f0c6bb5351/disk-9d9019bc.raw.xz
> > > > vmlinux: https://storage.googleapis.com/syzbot-assets/7eed8686df34/vmlinux-9d9019bc.xz
> > > > kernel image: https://storage.googleapis.com/syzbot-assets/84bb6da6b00e/bzImage-9d9019bc.xz
> > > >
> > > > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > > > Reported-by: syzbot+dac365e3ce07c3d0e496@syzkaller.appspotmail.com
> > > >
> > > > WARNING: can't access registers at entry_SYSCALL_64_after_hwframe+0x63/0xcd
> > >
> > >
> > > This is another splat of reports we started getting recently. Looks
> > > like this may be ORC unwinder related as well.
> >
> > Yeah... Also:
> >
> > https://lkml.kernel.org/lkml/202302161616.85f13863-oliver.sang@intel.com
> > https://lkml.kernel.org/lkml/CACT4Y+YzZb2vscjBLiJ-p-ghbu77o851gbESfE=nZebXqfgE4g@mail.gmail.com
> >
> > The problem seems to be commit ffb1b4a41016 ("x86/unwind/orc: Add
> > 'signal' field to ORC metadata") but right now I don't know why.
>
> Ah, figured it out:
>
> $ tools/objtool/objtool --dump=orc vmlinux |grep signal:1 |wc -l
> 0
>
> The 'signal' bit isn't getting propagated from the unwind hints to the
> ORC entries :-(
>
> Will post a fix shortly.
Thanks for the quick fix!
Let's tell syzbot:
#syz fix: objtool: Fix ORC 'signal' propagation
next prev parent reply other threads:[~2023-02-17 9:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 14:13 [syzbot] WARNING: can't access registers at entry_SYSCALL_64_after_hwframe syzbot
2023-02-16 15:14 ` Dmitry Vyukov
2023-02-16 18:51 ` Josh Poimboeuf
2023-02-16 20:26 ` Josh Poimboeuf
2023-02-17 9:05 ` Dmitry Vyukov [this message]
2023-02-21 5:09 ` syzbot
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='CACT4Y+aBV3d7kLjAZ1hHHbX=y8gTvfwrPsiohwV81PzRRjGkGQ@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=jpoimboe@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=syzbot+dac365e3ce07c3d0e496@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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;
as well as URLs for NNTP newsgroup(s).