general protection fault in filp_close
15 views
Skip to first unread message
syzbot
Sep 8, 2020, 2:29:22 PM9/8/20
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 59126901 Merge tag 'perf-tools-fixes-for-v5.9-2020-09-03' ..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14da96ed900000
kernel config: https://syzkaller.appspot.com/x/.config?x=3c5f6ce8d5b68299
dashboard link: https://syzkaller.appspot.com/bug?extid=65ec64eb4daa186c1bae
compiler: gcc (GCC) 10.1.0-syz 20200507
CC: [linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]
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+65ec64...@syzkaller.appspotmail.com
general protection fault, probably for non-canonical address 0xeeeeeaeee0e000fd: 0000 [#1] PREEMPT SMP KASAN
KASAN: maybe wild-memory-access in range [0x77777777070007e8-0x77777777070007ef]
CPU: 0 PID: 26140 Comm: syz-executor.5 Not tainted 5.9.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:filp_close+0x91/0x170 fs/open.c:1275
Code: 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 d2 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b 5d 28 48 8d 7b 78 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 a5 00 00 00 48 8b 5b 78 45 31 ed 48 85 db 74 10
RSP: 0018:ffffc90018b87ee8 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 7777777707000770 RCX: ffffffff81bdcd7b
RDX: 0eeeeeeee0e000fd RSI: ffffffff81bdcd89 RDI: 77777777070007e8
RBP: ffff888000103840 R08: 0000000000000000 R09: ffff8880001038bf
R10: 0000000000000000 R11: 0000000000000000 R12: ffff888051c01c00
R13: ffff8880001038b8 R14: 0000000000000000 R15: 0000000000000000
FS: 00000000036a5940(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b31a28000 CR3: 000000020eebe000 CR4: 00000000001526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__close_fd+0x2f/0x50 fs/file.c:671
__do_sys_close fs/open.c:1295 [inline]
__se_sys_close fs/open.c:1293 [inline]
__x64_sys_close+0x69/0x100 fs/open.c:1293
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x416f01
Code: 75 14 b8 03 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 04 1b 00 00 c3 48 83 ec 08 e8 0a fc ff ff 48 89 04 24 b8 03 00 00 00 0f 05 <48> 8b 3c 24 48 89 c2 e8 53 fc ff ff 48 89 d0 48 83 c4 08 48 3d 01
RSP: 002b:00007ffdfc83fcb0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 0000000000416f01
RDX: 0000000000000000 RSI: 00000000000006ac RDI: 0000000000000003
RBP: 0000000000000001 R08: 00000000bb1546ac R09: 00000000bb1546b0
R10: 00007ffdfc83fda0 R11: 0000000000000293 R12: 000000000118d940
R13: 000000000118d940 R14: ffffffffffffffff R15: 000000000118d08c
Modules linked in:
---[ end trace af5eaa0c4956518d ]---
RIP: 0010:filp_close+0x91/0x170 fs/open.c:1275
Code: 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 d2 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b 5d 28 48 8d 7b 78 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 a5 00 00 00 48 8b 5b 78 45 31 ed 48 85 db 74 10
RSP: 0018:ffffc90018b87ee8 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 7777777707000770 RCX: ffffffff81bdcd7b
RDX: 0eeeeeeee0e000fd RSI: ffffffff81bdcd89 RDI: 77777777070007e8
RBP: ffff888000103840 R08: 0000000000000000 R09: ffff8880001038bf
R10: 0000000000000000 R11: 0000000000000000 R12: ffff888051c01c00
R13: ffff8880001038b8 R14: 0000000000000000 R15: 0000000000000000
FS: 00000000036a5940(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000200012c0 CR3: 000000020eebe000 CR4: 00000000001526f0
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: 59126901 Merge tag 'perf-tools-fixes-for-v5.9-2020-09-03' ..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14da96ed900000
kernel config: https://syzkaller.appspot.com/x/.config?x=3c5f6ce8d5b68299
dashboard link: https://syzkaller.appspot.com/bug?extid=65ec64eb4daa186c1bae
compiler: gcc (GCC) 10.1.0-syz 20200507
CC: [linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]
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+65ec64...@syzkaller.appspotmail.com
general protection fault, probably for non-canonical address 0xeeeeeaeee0e000fd: 0000 [#1] PREEMPT SMP KASAN
KASAN: maybe wild-memory-access in range [0x77777777070007e8-0x77777777070007ef]
CPU: 0 PID: 26140 Comm: syz-executor.5 Not tainted 5.9.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:filp_close+0x91/0x170 fs/open.c:1275
Code: 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 d2 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b 5d 28 48 8d 7b 78 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 a5 00 00 00 48 8b 5b 78 45 31 ed 48 85 db 74 10
RSP: 0018:ffffc90018b87ee8 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 7777777707000770 RCX: ffffffff81bdcd7b
RDX: 0eeeeeeee0e000fd RSI: ffffffff81bdcd89 RDI: 77777777070007e8
RBP: ffff888000103840 R08: 0000000000000000 R09: ffff8880001038bf
R10: 0000000000000000 R11: 0000000000000000 R12: ffff888051c01c00
R13: ffff8880001038b8 R14: 0000000000000000 R15: 0000000000000000
FS: 00000000036a5940(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b31a28000 CR3: 000000020eebe000 CR4: 00000000001526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__close_fd+0x2f/0x50 fs/file.c:671
__do_sys_close fs/open.c:1295 [inline]
__se_sys_close fs/open.c:1293 [inline]
__x64_sys_close+0x69/0x100 fs/open.c:1293
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x416f01
Code: 75 14 b8 03 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 04 1b 00 00 c3 48 83 ec 08 e8 0a fc ff ff 48 89 04 24 b8 03 00 00 00 0f 05 <48> 8b 3c 24 48 89 c2 e8 53 fc ff ff 48 89 d0 48 83 c4 08 48 3d 01
RSP: 002b:00007ffdfc83fcb0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 0000000000416f01
RDX: 0000000000000000 RSI: 00000000000006ac RDI: 0000000000000003
RBP: 0000000000000001 R08: 00000000bb1546ac R09: 00000000bb1546b0
R10: 00007ffdfc83fda0 R11: 0000000000000293 R12: 000000000118d940
R13: 000000000118d940 R14: ffffffffffffffff R15: 000000000118d08c
Modules linked in:
---[ end trace af5eaa0c4956518d ]---
RIP: 0010:filp_close+0x91/0x170 fs/open.c:1275
Code: 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 d2 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b 5d 28 48 8d 7b 78 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 a5 00 00 00 48 8b 5b 78 45 31 ed 48 85 db 74 10
RSP: 0018:ffffc90018b87ee8 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 7777777707000770 RCX: ffffffff81bdcd7b
RDX: 0eeeeeeee0e000fd RSI: ffffffff81bdcd89 RDI: 77777777070007e8
RBP: ffff888000103840 R08: 0000000000000000 R09: ffff8880001038bf
R10: 0000000000000000 R11: 0000000000000000 R12: ffff888051c01c00
R13: ffff8880001038b8 R14: 0000000000000000 R15: 0000000000000000
FS: 00000000036a5940(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000200012c0 CR3: 000000020eebe000 CR4: 00000000001526f0
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
Dec 22, 2020, 7:29:09 AM12/22/20
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