From: syzbot <syzbot+87ccdc710b6af3fff875@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: general protection fault in reconfigure_super
Date: Thu, 13 Sep 2018 21:11:03 -0700 [thread overview]
Message-ID: <00000000000006d2340575cd03c6@google.com> (raw)
In-Reply-To: <000000000000701dac0575ac7d64@google.com>
syzbot has found a reproducer for the following crash on:
HEAD commit: f8dcd0279214 Add linux-next specific files for 20180913
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=157a3321400000
kernel config: https://syzkaller.appspot.com/x/.config?x=eb7f4703ab2604e5
dashboard link: https://syzkaller.appspot.com/bug?extid=87ccdc710b6af3fff875
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1747e21a400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10bd47da400000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+87ccdc710b6af3fff875@syzkaller.appspotmail.com
random: sshd: uninitialized urandom read (32 bytes read)
random: sshd: uninitialized urandom read (32 bytes read)
random: sshd: uninitialized urandom read (32 bytes read)
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 5563 Comm: syz-executor716 Not tainted
4.19.0-rc3-next-20180913+ #73
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:reconfigure_super+0x48e/0xbb0 fs/super.c:981
Code: 00 fc ff df 48 c1 ea 03 80 3c 02 00 0f 85 62 05 00 00 48 ba 00 00 00
00 00 fc ff df 48 8b 03 48 8d 78 30 48 89 f9 48 c1 e9 03 <80> 3c 11 00 0f
85 4d 05 00 00 48 8b 40 30 48 85 c0 48 89 85 20 ff
RSP: 0018:ffff8801b77278d8 EFLAGS: 00010206
RAX: 0000000000000000 RBX: ffff8801b77279f8 RCX: 0000000000000006
RDX: dffffc0000000000 RSI: ffffffff81cdbc5b RDI: 0000000000000030
RBP: ffff8801b77279c8 R08: ffff8801bb7781c0 R09: fffffbfff12c24e5
R10: fffffbfff12c24e5 R11: ffffffff8961272b R12: ffff8801d928e680
R13: 1ffff10036ee4f20 R14: 0000000000000000 R15: ffff8801b7727adc
FS: 0000000001f01880(0000) GS:ffff8801dac00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000200000c0 CR3: 00000001d93b7000 CR4: 00000000001406f0
Call Trace:
do_umount_root+0x2b1/0x320 fs/namespace.c:1434
do_umount fs/namespace.c:1504 [inline]
ksys_umount+0x8b6/0x1230 fs/namespace.c:1620
__do_sys_umount fs/namespace.c:1631 [inline]
__se_sys_umount fs/namespace.c:1629 [inline]
__x64_sys_umount+0x54/0x80 fs/namespace.c:1629
do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x440069
Code: 18 89 d0 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 48 89 f8 48 89 f7
48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff
ff 0f 83 fb 13 fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007ffcf308b4e8 EFLAGS: 00000217 ORIG_RAX: 00000000000000a6
RAX: ffffffffffffffda RBX: 0030656c69662f2e RCX: 0000000000440069
RDX: 0000000000440069 RSI: 0000000000000000 RDI: 0000000020000040
RBP: 00000000006ca018 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000217 R12: 00000000004018f0
R13: 0000000000401980 R14: 0000000000000000 R15: 0000000000000000
Modules linked in:
---[ end trace b41eea7577a38771 ]---
RIP: 0010:reconfigure_super+0x48e/0xbb0 fs/super.c:981
Code: 00 fc ff df 48 c1 ea 03 80 3c 02 00 0f 85 62 05 00 00 48 ba 00 00 00
00 00 fc ff df 48 8b 03 48 8d 78 30 48 89 f9 48 c1 e9 03 <80> 3c 11 00 0f
85 4d 05 00 00 48 8b 40 30 48 85 c0 48 89 85 20 ff
RSP: 0018:ffff8801b77278d8 EFLAGS: 00010206
RAX: 0000000000000000 RBX: ffff8801b77279f8 RCX: 0000000000000006
RDX: dffffc0000000000 RSI: ffffffff81cdbc5b RDI: 0000000000000030
RBP: ffff8801b77279c8 R08: ffff8801bb7781c0 R09: fffffbfff12c24e5
R10: fffffbfff12c24e5 R11: ffffffff8961272b R12: ffff8801d928e680
R13: 1ffff10036ee4f20 R14: 0000000000000000 R15: ffff8801b7727adc
FS: 0000000001f01880(0000) GS:ffff8801dac00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000200000c0 CR3: 00000001d93b7000 CR4: 00000000001406f0
prev parent reply other threads:[~2018-09-14 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 13:23 general protection fault in reconfigure_super syzbot
2018-09-14 4:11 ` syzbot [this message]
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=00000000000006d2340575cd03c6@google.com \
--to=syzbot+87ccdc710b6af3fff875@syzkaller.appspotmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.