syzbot


general protection fault in debugfs_remove (2)

Status: auto-closed as invalid on 2020/08/14 06:05
Reported-by: syzbot+667fa3e0c1194ac828b2@syzkaller.appspotmail.com
First crash: 1471d, last: 1471d
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 general protection fault in debugfs_remove 1 1740d 1740d 0/1 auto-closed as invalid on 2019/11/19 00:32
linux-4.14 general protection fault in debugfs_remove 1 1624d 1624d 0/1 auto-closed as invalid on 2020/03/13 21:23
linux-4.19 general protection fault in debugfs_remove (2) 1 1333d 1333d 0/1 auto-closed as invalid on 2020/12/30 03:06
upstream general protection fault in debugfs_remove fs 1 1838d 1829d 0/26 auto-closed as invalid on 2019/10/12 06:37

Sample crash report:
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
UDF-fs: error (device md0): udf_read_tagged: read failed, block=256, location=256
Modules linked in:
CPU: 1 PID: 27268 Comm: syz-executor.0 Not tainted 4.14.176-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff88809fec2640 task.stack: ffff888050d58000
RIP: 0010:perf_trace_lock+0xa9/0x4b0 include/trace/events/lock.h:39
RSP: 0018:ffff888050d5f9b8 EFLAGS: 00010006
UDF-fs: error (device md0): udf_read_tagged: read failed, block=512, location=512
RAX: dffffc0000000000 RBX: 1ffff1100a1abf54 RCX: 1ffffffff10279bc
RDX: 000000000000002b RSI: 0000000000000140 RDI: ffffffff87d6e6e0
RBP: ffff888050d5fa70 R08: 0000000000000001 R09: 0000000000000000
R10: ffff88809fec2f10 R11: ffff88809fec2640 R12: 1ffff1100a1abf3d
R13: 0000000000000000 R14: ffffffff87d6e660 R15: ffff888050d5fa48
FS:  00007fa013c2c700(0000) GS:ffff8880aeb00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000000b203000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 trace_lock_release include/trace/events/lock.h:58 [inline]
 lock_release+0x4df/0x7f0 kernel/locking/lockdep.c:4012
 up_write+0x17/0x60 kernel/locking/rwsem.c:115
 inode_unlock include/linux/fs.h:724 [inline]
 debugfs_remove fs/debugfs/inode.c:665 [inline]
 debugfs_remove+0xb2/0x110 fs/debugfs/inode.c:654
 blk_trace_free+0x59/0x130 kernel/trace/blktrace.c:325
 do_blk_trace_setup+0x717/0xad0 kernel/trace/blktrace.c:564
 blk_trace_setup+0xa3/0x120 kernel/trace/blktrace.c:579
 sg_ioctl+0x2f9/0x2620 drivers/scsi/sg.c:1127
 vfs_ioctl fs/ioctl.c:46 [inline]
 file_ioctl fs/ioctl.c:500 [inline]
 do_vfs_ioctl+0x75a/0xfe0 fs/ioctl.c:684
 SYSC_ioctl fs/ioctl.c:701 [inline]
 SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692
 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
 entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x45c889
RSP: 002b:00007fa013c2bc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fa013c2c6d4 RCX: 000000000045c889
RDX: 0000000020000080 RSI: 00000000c0481273 RDI: 0000000000000009
RBP: 000000000076bfa0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 000000000000022a R14: 00000000004c4553 R15: 000000000076bfac
Code: 00 48 8b 85 70 ff ff ff 4d 8b ae 80 00 00 00 48 83 c0 18 48 89 c2 48 89 85 60 ff ff ff 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 <80> 3c 02 00 0f 85 e7 02 00 00 48 8b 85 70 ff ff ff 48 8b 78 18 
RIP: perf_trace_lock+0xa9/0x4b0 include/trace/events/lock.h:39 RSP: ffff888050d5f9b8
---[ end trace e5fdf397d53cf6fa ]---

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/04/16 06:04 linux-4.14.y c10b57a567e4 c743fcb3 .config console log report ci2-linux-4-14
* Struck through repros no longer work on HEAD.