stack segment fault in blk_add_driver_data

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d09b8017 Linux 4.19.147
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14dff3d9900000
kernel config: https://syzkaller.appspot.com/x/.config?x=47cc70be3c316a0a
dashboard link: https://syzkaller.appspot.com/bug?extid=e321098e0034a7fd37b2
compiler: gcc (GCC) 10.1.0-syz 20200507

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+e32109...@syzkaller.appspotmail.com

ntfs: (device loop1): ntfs_fill_super(): Not an NTFS volume.
ntfs: (device loop1): read_ntfs_boot_sector(): Primary boot sector is invalid.
ntfs: (device loop1): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
ntfs: (device loop1): ntfs_fill_super(): Not an NTFS volume.
ntfs: volume version 3.1.
stack segment: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 6167 Comm: syz-executor.5 Not tainted 4.19.147-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:rcu_read_unlock include/linux/rcupdate.h:677 [inline]
RIP: 0010:blk_add_driver_data+0x140/0x4b0 kernel/trace/blktrace.c:1136
Code: 00 fa ff 31 ff 4c 89 ee e8 ad 01 fa ff 4d 85 ed 0f 85 5f 01 00 00 e8 0f 00 fa ff e8 4a 52 e6 ff 31 ff 89 c3 89 c6 e8 6f 01 fa <ff> 85 db 74 3a e8 f6 ff f9 ff 0f b6 1d a6 a8 bb 09 bf 01 00 00 00
RSP: 0018:ffff888058c8fee8 EFLAGS: 00010293
RAX: ffff88805b5c0700 RBX: 0000000000000002 RCX: ffffffff81008568
RDX: 0000000000000000 RSI: ffffffff81008576 RDI: 0000000000000005
RBP: dffffc0000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff888058c8ff58
R13: ffffed100b6b80e0 R14: ffff88805b5c0700 R15: 0000000000000002
FS: 000000000188d940(0000) GS:ffff8880ae300000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fff42902d7c CR3: 000000004ca2c000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x57c/0x670 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45c367
Code: 8b 32 0f 05 31 c0 64 89 32 e9 77 ff ff ff 0f 1f 44 00 00 48 85 ff 74 3b 53 8b 1f e8 53 a9 fd ff 48 63 fb b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 09 5b c3 0f 1f 80 00 00 00 00 48 c7 c2 d4 ff
RSP: 002b:00007fff42903480 EFLAGS: 00000202 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000003 RCX: 000000000045c367
RDX: 0000000000000000 RSI: 000000000074c678 RDI: 0000000000000003
RBP: 0000000000000e9d R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000006 R11: 0000000000000202 R12: 00007fff429045c0
R13: 000000000188ea60 R14: 0000000000000000 R15: 00007fff429045c0
Modules linked in:
---[ end trace d165460dc529ea33 ]---
RIP: 0010:rcu_read_unlock include/linux/rcupdate.h:677 [inline]
RIP: 0010:blk_add_driver_data+0x140/0x4b0 kernel/trace/blktrace.c:1136
Code: 00 fa ff 31 ff 4c 89 ee e8 ad 01 fa ff 4d 85 ed 0f 85 5f 01 00 00 e8 0f 00 fa ff e8 4a 52 e6 ff 31 ff 89 c3 89 c6 e8 6f 01 fa <ff> 85 db 74 3a e8 f6 ff f9 ff 0f b6 1d a6 a8 bb 09 bf 01 00 00 00
RSP: 0018:ffff888058c8fee8 EFLAGS: 00010293
RAX: ffff88805b5c0700 RBX: 0000000000000002 RCX: ffffffff81008568
RDX: 0000000000000000 RSI: ffffffff81008576 RDI: 0000000000000005
RBP: dffffc0000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff888058c8ff58
R13: ffffed100b6b80e0 R14: ffff88805b5c0700 R15: 0000000000000002
FS: 000000000188d940(0000) GS:ffff8880ae300000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fff42902d7c CR3: 000000004ca2c000 CR4: 00000000001426e0
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]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.