From: syzbot <syzbot+dac365e3ce07c3d0e496@syzkaller.appspotmail.com>
To: dvyukov@google.com, jpoimboe@kernel.org, jpoimboe@redhat.com,
linux-kernel@vger.kernel.org, mingo@kernel.org,
peterz@infradead.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING: can't access registers at entry_SYSCALL_64_after_hwframe
Date: Mon, 20 Feb 2023 21:09:45 -0800 [thread overview]
Message-ID: <000000000000b8643205f52ec9bf@google.com> (raw)
In-Reply-To: <000000000000ff304105f4d1cd36@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: d2af0fa4bfa4 Add linux-next specific files for 20230220
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=109146a0c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=594e1a56901fd35d
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
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10b9f4d8c80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=138179e8c80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/83b78c113e8e/disk-d2af0fa4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d59f9b2c9091/vmlinux-d2af0fa4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2726c16c1d3b/bzImage-d2af0fa4.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
prev parent reply other threads:[~2023-02-21 5:09 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
2023-02-21 5:09 ` syzbot [this message]
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=000000000000b8643205f52ec9bf@google.com \
--to=syzbot+dac365e3ce07c3d0e496@syzkaller.appspotmail.com \
--cc=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=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 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.