linux-kernel - Re: [syzbot] WARNING: can't access registers at entry_SYSCALL_64_after

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACT4Y+aBV3d7kLjAZ1hHHbX=y8gTvfwrPsiohwV81PzRRjGkGQ@mail.gmail.com>
Date:   Fri, 17 Feb 2023 10:05:52 +0100
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Josh Poimboeuf <jpoimboe@...nel.org>
Cc:     syzbot <syzbot+dac365e3ce07c3d0e496@...kaller.appspotmail.com>,
        Josh Poimboeuf <jpoimboe@...hat.com>,
        Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org,
        syzkaller-bugs@...glegroups.com,
        Peter Zijlstra <peterz@...radead.org>
Subject: Re: [syzbot] WARNING: can't access registers at entry_SYSCALL_64_after_hwframe

On Thu, 16 Feb 2023 at 21:26, Josh Poimboeuf <jpoimboe@...nel.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@...kaller.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