From: linmiaohe <linmiaohe@huawei.com>
To: syzbot <syzbot+c5d5a51dcbb558ca0cb5@syzkaller.appspotmail.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"hdanton@sina.com" <hdanton@sina.com>,
"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: Tue, 15 Sep 2020 11:13:20 +0000 [thread overview]
Message-ID: <e3b337ff2fcc4b2c955be20aed74477c@huawei.com> (raw)
syzbot <syzbot+c5d5a51dcbb558ca0cb5@syzkaller.appspotmail.com> wrote:
> Hello,
>
>syzbot has tested the proposed patch but the reproducer is still triggering an issue:
>kernel panic: corrupted stack end in sys_nanosleep
>
>Kernel panic - not syncing: corrupted stack end detected inside scheduler
>CPU: 0 PID: 13791 Comm: syz-executor.4 Not tainted 5.9.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace:
> __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x198/0x1fd lib/dump_stack.c:118
> panic+0x347/0x7c0 kernel/panic.c:231
> schedule_debug kernel/sched/core.c:4278 [inline]
> __schedule+0x221e/0x2230 kernel/sched/core.c:4422
> schedule+0xd0/0x2a0 kernel/sched/core.c:4602 freezable_schedule include/linux/freezer.h:172 [inline]
> do_nanosleep+0x222/0x650 kernel/time/hrtimer.c:1883
> hrtimer_nanosleep+0x1f9/0x430 kernel/time/hrtimer.c:1936 __do_sys_nanosleep kernel/time/hrtimer.c:1970 [inline] __se_sys_nanosleep kernel/time/hrtimer.c:1957 [inline]
> __x64_sys_nanosleep+0x1dc/0x260 kernel/time/hrtimer.c:1957
> do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
> entry_SYSCALL_64_after_hwframe+0x44/0xa9
>RIP: 0033:0x45ba81
>Code: 75 14 b8 23 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 84 cf fb ff c3 48 83 ec 08 e8 ea 46 00 00 48 89 04 24 b8 23 00 00 00 0f 05 <48> 8b 3c 24 48 89 c2 e8 33 47 00 00 48 89 d0 48 83 c4 08 48 3d 01
>RSP: 002b:00007ffca6cb6d70 EFLAGS: 00000293 ORIG_RAX: 0000000000000023
>RAX: ffffffffffffffda RBX: 000000000002f226 RCX: 000000000045ba81
>RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00007ffca6cb6d80
>RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000
>R10: 00007ffca6cb6e80 R11: 0000000000000293 R12: 000000000118cf40
>R13: 000000000118d940 R14: ffffffffffffffff R15: 000000000118cfec Kernel Offset: disabled Rebooting in 86400 seconds..
>
>
>Tested on:
>
>commit: 796cd8f4 fix gpf
>git tree: https://github.com/Linmiaohe/linux/
>console output: https://syzkaller.appspot.com/x/log.txt?x=12b5d501900000
>kernel config: https://syzkaller.appspot.com/x/.config?x=f82e58a6661a5ac4
>dashboard link: https://syzkaller.appspot.com/bug?extid=c5d5a51dcbb558ca0cb5
>compiler: gcc (GCC) 10.1.0-syz 20200507
This issue looks like irrelevant with my previous commit, maybe it's because I fix this on wrong commit.
I would rebase this on commit 59126901 ("Merge tag 'perf-tools-fixes-for-v5.9-2020-09-03' ..").
Thanks.
next reply other threads:[~2020-09-15 11:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 11:13 linmiaohe [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-16 9:05 linmiaohe
2020-09-16 6:50 linmiaohe
2020-09-16 8:39 ` syzbot
2020-09-16 1:48 linmiaohe
2020-09-16 4:24 ` syzbot
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=e3b337ff2fcc4b2c955be20aed74477c@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=hdanton@sina.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