From: syzbot <syzbot+2698183e871d8a137f9d@syzkaller.appspotmail.com>
To: bp@alien8.de, bp@suse.de, dave.hansen@linux.intel.com,
hpa@zytor.com, keescook@chromium.org, krisman@collabora.com,
liangjs@pku.edu.cn, linux-kernel@vger.kernel.org,
luto@kernel.org, mingo@redhat.com, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
wad@chromium.org, x86@kernel.org
Subject: Re: [syzbot] WARNING in emulate_vsyscall
Date: Tue, 26 Oct 2021 21:20:12 -0700 [thread overview]
Message-ID: <0000000000000477e405cf4de9b8@google.com> (raw)
In-Reply-To: <000000000000016ca805beaf4d26@google.com>
syzbot suspects this issue was fixed by commit:
commit d4ffd5df9d18031b6a53f934388726775b4452d3
Author: Jiashuo Liang <liangjs@pku.edu.cn>
Date: Fri Jul 30 03:01:52 2021 +0000
x86/fault: Fix wrong signal when vsyscall fails with pkey
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11bb466f300000
start commit: 009c9aa5be65 Linux 5.13-rc6
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=7ca96a2d153c74b0
dashboard link: https://syzkaller.appspot.com/bug?extid=2698183e871d8a137f9d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e1a704300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=125a92d0300000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: x86/fault: Fix wrong signal when vsyscall fails with pkey
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-10-27 4:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 16:23 [syzbot] WARNING in emulate_vsyscall syzbot
2021-10-27 4:20 ` syzbot [this message]
2021-10-28 13:01 ` Dmitry Vyukov
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=0000000000000477e405cf4de9b8@google.com \
--to=syzbot+2698183e871d8a137f9d@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=krisman@collabora.com \
--cc=liangjs@pku.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=wad@chromium.org \
--cc=x86@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