general protection fault in find_entry (3)
5 views
Skip to first unread message
syzbot
May 6, 2021, 2:44:17 PM5/6/21
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: e3d35712 Add linux-next specific files for 20210423
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=114a6909d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=e370221d7500b26a
dashboard link: https://syzkaller.appspot.com/bug?extid=acefa31193cebfd80957
CC: [adob...@gmail.com and...@kernel.org a...@kernel.org b...@vger.kernel.org dan...@iogearbox.net john.fa...@gmail.com ka...@fb.com kees...@chromium.org kps...@kernel.org linux-...@vger.kernel.org linux-...@vger.kernel.org mcg...@kernel.org net...@vger.kernel.org songliu...@fb.com y...@fb.com yza...@google.com]
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+acefa3...@syzkaller.appspotmail.com
general protection fault, probably for non-canonical address 0xe00000201ffffd40: 0000 [#1] PREEMPT SMP KASAN
KASAN: probably user-memory-access in range [0x00002100ffffea00-0x00002100ffffea07]
CPU: 0 PID: 8428 Comm: syz-executor Not tainted 5.12.0-rc8-next-20210423-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:find_entry.isra.0+0xdd/0x1e0 fs/proc/proc_sysctl.c:122
Code: 89 f8 48 c1 e8 03 42 80 3c 28 00 0f 85 d1 00 00 00 49 89 dc 4d 2b 66 40 49 c1 fc 05 49 c1 e4 06 49 01 ec 4c 89 e0 48 c1 e8 03 <42> 80 3c 28 00 0f 85 a0 00 00 00 49 8b 2c 24 48 89 ef e8 0c 3e fb
RSP: 0018:ffffc9000167f840 EFLAGS: 00010202
RAX: 000004201ffffd40 RBX: ffff888024c40050 RCX: 0000000000000000
RDX: ffff88802530b900 RSI: ffffffff81eef73f RDI: ffff888024c40040
RBP: 00002100ffffea00 R08: 0000000000000000 R09: 0000000000000003
R10: ffffffff81eef705 R11: 0000000000000000 R12: 00002100ffffea00
R13: dffffc0000000000 R14: ffff888024c40000 R15: 0000000000000010
FS: 00000000028e9400(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000004af0b8 CR3: 000000001a187000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
lookup_entry fs/proc/proc_sysctl.c:339 [inline]
proc_sys_lookup+0x171/0x590 fs/proc/proc_sysctl.c:512
lookup_open.isra.0+0x69f/0x13d0 fs/namei.c:3193
open_last_lookups fs/namei.c:3285 [inline]
path_openat+0x9af/0x27d0 fs/namei.c:3491
do_filp_open+0x190/0x3d0 fs/namei.c:3521
do_sys_openat2+0x16d/0x420 fs/open.c:1187
do_sys_open fs/open.c:1203 [inline]
__do_sys_openat fs/open.c:1219 [inline]
__se_sys_openat fs/open.c:1214 [inline]
__x64_sys_openat+0x13f/0x1f0 fs/open.c:1214
do_syscall_64+0x3a/0xb0 arch/x86/entry/common.c:47
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x419667
Code: 25 00 00 41 00 3d 00 00 41 00 74 47 64 8b 04 25 18 00 00 00 85 c0 75 6b 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 95 00 00 00 48 8b 4c 24 28 64 48 2b 0c 25
RSP: 002b:00007ffd2d55d2d0 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0000000000000007 RCX: 0000000000419667
RDX: 0000000000080001 RSI: 00000000004af1d0 RDI: 00000000ffffff9c
RBP: 00000000004af1d0 R08: 0000000000000000 R09: 00007ffd2d55d2c0
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000080001
R13: 00007ffd2d55d370 R14: 0000000000000000 R15: 0000000000400538
Modules linked in:
---[ end trace 804386bbb2e8477f ]---
RIP: 0010:find_entry.isra.0+0xdd/0x1e0 fs/proc/proc_sysctl.c:122
Code: 89 f8 48 c1 e8 03 42 80 3c 28 00 0f 85 d1 00 00 00 49 89 dc 4d 2b 66 40 49 c1 fc 05 49 c1 e4 06 49 01 ec 4c 89 e0 48 c1 e8 03 <42> 80 3c 28 00 0f 85 a0 00 00 00 49 8b 2c 24 48 89 ef e8 0c 3e fb
RSP: 0018:ffffc9000167f840 EFLAGS: 00010202
RAX: 000004201ffffd40 RBX: ffff888024c40050 RCX: 0000000000000000
RDX: ffff88802530b900 RSI: ffffffff81eef73f RDI: ffff888024c40040
RBP: 00002100ffffea00 R08: 0000000000000000 R09: 0000000000000003
R10: ffffffff81eef705 R11: 0000000000000000 R12: 00002100ffffea00
R13: dffffc0000000000 R14: ffff888024c40000 R15: 0000000000000010
FS: 00000000028e9400(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000004af0b8 CR3: 000000001a187000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot found the following issue on:
HEAD commit: e3d35712 Add linux-next specific files for 20210423
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=114a6909d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=e370221d7500b26a
dashboard link: https://syzkaller.appspot.com/bug?extid=acefa31193cebfd80957
CC: [adob...@gmail.com and...@kernel.org a...@kernel.org b...@vger.kernel.org dan...@iogearbox.net john.fa...@gmail.com ka...@fb.com kees...@chromium.org kps...@kernel.org linux-...@vger.kernel.org linux-...@vger.kernel.org mcg...@kernel.org net...@vger.kernel.org songliu...@fb.com y...@fb.com yza...@google.com]
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+acefa3...@syzkaller.appspotmail.com
general protection fault, probably for non-canonical address 0xe00000201ffffd40: 0000 [#1] PREEMPT SMP KASAN
KASAN: probably user-memory-access in range [0x00002100ffffea00-0x00002100ffffea07]
CPU: 0 PID: 8428 Comm: syz-executor Not tainted 5.12.0-rc8-next-20210423-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:find_entry.isra.0+0xdd/0x1e0 fs/proc/proc_sysctl.c:122
Code: 89 f8 48 c1 e8 03 42 80 3c 28 00 0f 85 d1 00 00 00 49 89 dc 4d 2b 66 40 49 c1 fc 05 49 c1 e4 06 49 01 ec 4c 89 e0 48 c1 e8 03 <42> 80 3c 28 00 0f 85 a0 00 00 00 49 8b 2c 24 48 89 ef e8 0c 3e fb
RSP: 0018:ffffc9000167f840 EFLAGS: 00010202
RAX: 000004201ffffd40 RBX: ffff888024c40050 RCX: 0000000000000000
RDX: ffff88802530b900 RSI: ffffffff81eef73f RDI: ffff888024c40040
RBP: 00002100ffffea00 R08: 0000000000000000 R09: 0000000000000003
R10: ffffffff81eef705 R11: 0000000000000000 R12: 00002100ffffea00
R13: dffffc0000000000 R14: ffff888024c40000 R15: 0000000000000010
FS: 00000000028e9400(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000004af0b8 CR3: 000000001a187000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
lookup_entry fs/proc/proc_sysctl.c:339 [inline]
proc_sys_lookup+0x171/0x590 fs/proc/proc_sysctl.c:512
lookup_open.isra.0+0x69f/0x13d0 fs/namei.c:3193
open_last_lookups fs/namei.c:3285 [inline]
path_openat+0x9af/0x27d0 fs/namei.c:3491
do_filp_open+0x190/0x3d0 fs/namei.c:3521
do_sys_openat2+0x16d/0x420 fs/open.c:1187
do_sys_open fs/open.c:1203 [inline]
__do_sys_openat fs/open.c:1219 [inline]
__se_sys_openat fs/open.c:1214 [inline]
__x64_sys_openat+0x13f/0x1f0 fs/open.c:1214
do_syscall_64+0x3a/0xb0 arch/x86/entry/common.c:47
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x419667
Code: 25 00 00 41 00 3d 00 00 41 00 74 47 64 8b 04 25 18 00 00 00 85 c0 75 6b 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 95 00 00 00 48 8b 4c 24 28 64 48 2b 0c 25
RSP: 002b:00007ffd2d55d2d0 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0000000000000007 RCX: 0000000000419667
RDX: 0000000000080001 RSI: 00000000004af1d0 RDI: 00000000ffffff9c
RBP: 00000000004af1d0 R08: 0000000000000000 R09: 00007ffd2d55d2c0
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000080001
R13: 00007ffd2d55d370 R14: 0000000000000000 R15: 0000000000400538
Modules linked in:
---[ end trace 804386bbb2e8477f ]---
RIP: 0010:find_entry.isra.0+0xdd/0x1e0 fs/proc/proc_sysctl.c:122
Code: 89 f8 48 c1 e8 03 42 80 3c 28 00 0f 85 d1 00 00 00 49 89 dc 4d 2b 66 40 49 c1 fc 05 49 c1 e4 06 49 01 ec 4c 89 e0 48 c1 e8 03 <42> 80 3c 28 00 0f 85 a0 00 00 00 49 8b 2c 24 48 89 ef e8 0c 3e fb
RSP: 0018:ffffc9000167f840 EFLAGS: 00010202
RAX: 000004201ffffd40 RBX: ffff888024c40050 RCX: 0000000000000000
RDX: ffff88802530b900 RSI: ffffffff81eef73f RDI: ffff888024c40040
RBP: 00002100ffffea00 R08: 0000000000000000 R09: 0000000000000003
R10: ffffffff81eef705 R11: 0000000000000000 R12: 00002100ffffea00
R13: dffffc0000000000 R14: ffff888024c40000 R15: 0000000000000010
FS: 00000000028e9400(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000004af0b8 CR3: 000000001a187000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot
Jul 1, 2021, 2:40:12 PM7/1/21
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages