From: linmiaohe <linmiaohe@huawei.com>
To: syzbot <syzbot+c5d5a51dcbb558ca0cb5@syzkaller.appspotmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"syzkaller-bugs@googlegroups.com"
<syzkaller-bugs@googlegroups.com>
Subject: Re: general protection fault in unlink_file_vma
Date: Wed, 16 Sep 2020 06:50:09 +0000 [thread overview]
Message-ID: <d3a7e455690b4c629145c8c4936a55c7@huawei.com> (raw)
>
>Hello,
>
>syzbot has tested the proposed patch but the reproducer is still triggering an issue:
>kernel panic: Fatal exception
>
>RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000
>R10: 00007ffd30630720 R11: 0000000000000000 R12: 000000000118d940
>R13: 000000000118d940 R14: ffffffffffffffff R15: 000000000118cfec
>FS: 0000000001b47940(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
>CS: 0033 DS: 0000 ES: 0000 CR0: 0000000080050033
>CR2: 0000000001590004 CR3: 0000000021097000 CR4: 00000000001506e0
>DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
>DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Kernel panic - not syncing: Fatal exception Kernel Offset: disabled
>
>
>Tested on:
>
>commit: 8f79400b fix vma_merge gpf
>git tree: https://github.com/Linmiaohe/linux vma_merge_fix
>console output: https://syzkaller.appspot.com/x/log.txt?x=153b1d43900000
>kernel config: https://syzkaller.appspot.com/x/.config?x=3c5f6ce8d5b68299
>dashboard link: https://syzkaller.appspot.com/bug?extid=c5d5a51dcbb558ca0cb5
>compiler: gcc (GCC) 10.1.0-syz 20200507
>
#syz test: https://github.com/Linmiaohe/linux vma_merge_fix
next reply other threads:[~2020-09-16 6:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 6:50 linmiaohe [this message]
2020-09-16 8:39 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2020-09-16 9:05 linmiaohe
2020-09-16 1:48 linmiaohe
2020-09-16 4:24 ` syzbot
2020-09-15 11:13 linmiaohe
2020-09-14 6:42 linmiaohe
2020-09-14 1:51 linmiaohe
2020-09-13 9:17 linmiaohe
2020-09-13 11:16 ` Hillf Danton
2020-09-10 6:26 linmiaohe
2020-09-09 0:19 syzbot
2020-09-09 4:15 ` Hillf Danton
2020-09-10 2:13 ` Souptick Joarder
2020-09-10 4:17 ` Hillf Danton
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=d3a7e455690b4c629145c8c4936a55c7@huawei.com \
--to=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+c5d5a51dcbb558ca0cb5@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