[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0000000000000477e405cf4de9b8@google.com>
Date: Tue, 26 Oct 2021 21:20:12 -0700
From: syzbot <syzbot+2698183e871d8a137f9d@...kaller.appspotmail.com>
To: bp@...en8.de, bp@...e.de, dave.hansen@...ux.intel.com,
hpa@...or.com, keescook@...omium.org, krisman@...labora.com,
liangjs@....edu.cn, linux-kernel@...r.kernel.org, luto@...nel.org,
mingo@...hat.com, peterz@...radead.org,
syzkaller-bugs@...glegroups.com, tglx@...utronix.de,
wad@...omium.org, x86@...nel.org
Subject: Re: [syzbot] WARNING in emulate_vsyscall
syzbot suspects this issue was fixed by commit:
commit d4ffd5df9d18031b6a53f934388726775b4452d3
Author: Jiashuo Liang <liangjs@....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
Powered by blists - more mailing lists