[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <d3a7e455690b4c629145c8c4936a55c7@huawei.com>
Date: Wed, 16 Sep 2020 06:50:09 +0000
From: linmiaohe <linmiaohe@...wei.com>
To: syzbot <syzbot+c5d5a51dcbb558ca0cb5@...kaller.appspotmail.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"syzkaller-bugs@...glegroups.com" <syzkaller-bugs@...glegroups.com>
Subject: Re: general protection fault in unlink_file_vma
>
>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
Powered by blists - more mailing lists