[syzbot] invalid opcode in writeback_single_inode
12 views
Skip to first unread message
syzbot
Sep 24, 2022, 4:08:39 AM9/24/22
to linux-...@vger.kernel.org, linux-...@vger.kernel.org, syzkall...@googlegroups.com, vi...@zeniv.linux.org.uk
Hello,
syzbot found the following issue on:
HEAD commit: dc164f4fb00a Merge tag 'for-linus-6.0-rc7' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=132e8dd5080000
kernel config: https://syzkaller.appspot.com/x/.config?x=7db7ad17eb14cb7
dashboard link: https://syzkaller.appspot.com/bug?extid=15cb24a539075fc4c472
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/853950e33581/disk-dc164f4f.raw.xz
vmlinux: https://storage.googleapis.com/1359f09c5a19/vmlinux-dc164f4f.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+15cb24...@syzkaller.appspotmail.com
loop5: detected capacity change from 0 to 8189
ntfs3: loop5: Different NTFS' sector size (1024) and media sector size (512)
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 11292 Comm: syz-executor.5 Not tainted 6.0.0-rc6-syzkaller-00045-gdc164f4fb00a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/16/2022
RIP: 0010:spin_lock include/linux/spinlock.h:349 [inline]
RIP: 0010:writeback_single_inode+0x2e/0x4c0 fs/fs-writeback.c:1676
Code: 41 55 41 54 49 89 f4 55 48 89 fd 53 4c 8d b5 88 00 00 00 4c 8d ad 08 02 00 00 48 83 ec 08 e8 b9 12 99 ff 4c 89 f7 e8 31 f0 a0 <07> be 04 00 00 00 4c 89 ef e8 94 b3 e4 ff 4c 89 ea 48 b8 00 00 00
RSP: 0018:ffffc90004dd7a10 EFLAGS: 00010292
RAX: 0000000000000000 RBX: 1ffff920009baf4b RCX: ffffffff815f1e80
RDX: 1ffff11006c6606d RSI: 0000000000000004 RDI: ffffc90004dd79a0
RBP: ffff8880363302d0 R08: 0000000000000001 R09: 0000000000000003
R10: fffff520009baf34 R11: 0000000000000000 R12: ffffc90004dd7a88
R13: ffff8880363304d8 R14: ffff888036330358 R15: ffff8880363303a8
FS: 00007efc6583b700(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020075000 CR3: 000000001d8c1000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
write_inode_now+0x16a/0x1e0 fs/fs-writeback.c:2723
iput_final fs/inode.c:1735 [inline]
iput.part.0+0x45b/0x810 fs/inode.c:1774
iput+0x58/0x70 fs/inode.c:1764
ntfs_fill_super+0x2e89/0x37f0 fs/ntfs3/super.c:1190
get_tree_bdev+0x440/0x760 fs/super.c:1323
vfs_get_tree+0x89/0x2f0 fs/super.c:1530
do_new_mount fs/namespace.c:3040 [inline]
path_mount+0x1326/0x1e20 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__x64_sys_mount+0x27f/0x300 fs/namespace.c:3568
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7efc6468bb9a
Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007efc6583af88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 00007efc6468bb9a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007efc6583afe0
RBP: 00007efc6583b020 R08: 00007efc6583b020 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000000
R13: 0000000020000100 R14: 00007efc6583afe0 R15: 000000002007c6a0
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:spin_lock include/linux/spinlock.h:349 [inline]
RIP: 0010:writeback_single_inode+0x2e/0x4c0 fs/fs-writeback.c:1676
Code: 41 55 41 54 49 89 f4 55 48 89 fd 53 4c 8d b5 88 00 00 00 4c 8d ad 08 02 00 00 48 83 ec 08 e8 b9 12 99 ff 4c 89 f7 e8 31 f0 a0 <07> be 04 00 00 00 4c 89 ef e8 94 b3 e4 ff 4c 89 ea 48 b8 00 00 00
RSP: 0018:ffffc90004dd7a10 EFLAGS: 00010292
RAX: 0000000000000000 RBX: 1ffff920009baf4b RCX: ffffffff815f1e80
RDX: 1ffff11006c6606d RSI: 0000000000000004 RDI: ffffc90004dd79a0
RBP: ffff8880363302d0 R08: 0000000000000001 R09: 0000000000000003
R10: fffff520009baf34 R11: 0000000000000000 R12: ffffc90004dd7a88
R13: ffff8880363304d8 R14: ffff888036330358 R15: ffff8880363303a8
FS: 00007efc6583b700(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020075000 CR3: 000000001d8c1000 CR4: 00000000003506e0
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: dc164f4fb00a Merge tag 'for-linus-6.0-rc7' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=132e8dd5080000
kernel config: https://syzkaller.appspot.com/x/.config?x=7db7ad17eb14cb7
dashboard link: https://syzkaller.appspot.com/bug?extid=15cb24a539075fc4c472
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/853950e33581/disk-dc164f4f.raw.xz
vmlinux: https://storage.googleapis.com/1359f09c5a19/vmlinux-dc164f4f.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+15cb24...@syzkaller.appspotmail.com
loop5: detected capacity change from 0 to 8189
ntfs3: loop5: Different NTFS' sector size (1024) and media sector size (512)
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 11292 Comm: syz-executor.5 Not tainted 6.0.0-rc6-syzkaller-00045-gdc164f4fb00a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/16/2022
RIP: 0010:spin_lock include/linux/spinlock.h:349 [inline]
RIP: 0010:writeback_single_inode+0x2e/0x4c0 fs/fs-writeback.c:1676
Code: 41 55 41 54 49 89 f4 55 48 89 fd 53 4c 8d b5 88 00 00 00 4c 8d ad 08 02 00 00 48 83 ec 08 e8 b9 12 99 ff 4c 89 f7 e8 31 f0 a0 <07> be 04 00 00 00 4c 89 ef e8 94 b3 e4 ff 4c 89 ea 48 b8 00 00 00
RSP: 0018:ffffc90004dd7a10 EFLAGS: 00010292
RAX: 0000000000000000 RBX: 1ffff920009baf4b RCX: ffffffff815f1e80
RDX: 1ffff11006c6606d RSI: 0000000000000004 RDI: ffffc90004dd79a0
RBP: ffff8880363302d0 R08: 0000000000000001 R09: 0000000000000003
R10: fffff520009baf34 R11: 0000000000000000 R12: ffffc90004dd7a88
R13: ffff8880363304d8 R14: ffff888036330358 R15: ffff8880363303a8
FS: 00007efc6583b700(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020075000 CR3: 000000001d8c1000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
write_inode_now+0x16a/0x1e0 fs/fs-writeback.c:2723
iput_final fs/inode.c:1735 [inline]
iput.part.0+0x45b/0x810 fs/inode.c:1774
iput+0x58/0x70 fs/inode.c:1764
ntfs_fill_super+0x2e89/0x37f0 fs/ntfs3/super.c:1190
get_tree_bdev+0x440/0x760 fs/super.c:1323
vfs_get_tree+0x89/0x2f0 fs/super.c:1530
do_new_mount fs/namespace.c:3040 [inline]
path_mount+0x1326/0x1e20 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__x64_sys_mount+0x27f/0x300 fs/namespace.c:3568
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7efc6468bb9a
Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007efc6583af88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 00007efc6468bb9a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007efc6583afe0
RBP: 00007efc6583b020 R08: 00007efc6583b020 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000000
R13: 0000000020000100 R14: 00007efc6583afe0 R15: 000000002007c6a0
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:spin_lock include/linux/spinlock.h:349 [inline]
RIP: 0010:writeback_single_inode+0x2e/0x4c0 fs/fs-writeback.c:1676
Code: 41 55 41 54 49 89 f4 55 48 89 fd 53 4c 8d b5 88 00 00 00 4c 8d ad 08 02 00 00 48 83 ec 08 e8 b9 12 99 ff 4c 89 f7 e8 31 f0 a0 <07> be 04 00 00 00 4c 89 ef e8 94 b3 e4 ff 4c 89 ea 48 b8 00 00 00
RSP: 0018:ffffc90004dd7a10 EFLAGS: 00010292
RAX: 0000000000000000 RBX: 1ffff920009baf4b RCX: ffffffff815f1e80
RDX: 1ffff11006c6606d RSI: 0000000000000004 RDI: ffffc90004dd79a0
RBP: ffff8880363302d0 R08: 0000000000000001 R09: 0000000000000003
R10: fffff520009baf34 R11: 0000000000000000 R12: ffffc90004dd7a88
R13: ffff8880363304d8 R14: ffff888036330358 R15: ffff8880363303a8
FS: 00007efc6583b700(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020075000 CR3: 000000001d8c1000 CR4: 00000000003506e0
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
Oct 2, 2022, 2:22:36 PM10/2/22
to almaz.ale...@paragon-software.com, linux-...@vger.kernel.org, linux-...@vger.kernel.org, ll...@lists.linux.dev, nat...@kernel.org, ndesau...@google.com, nt...@lists.linux.dev, syzkall...@googlegroups.com, tr...@redhat.com, vi...@zeniv.linux.org.uk
syzbot has found a reproducer for the following issue on:
HEAD commit: b357fd1c2afc Merge tag 'usb-6.0-final' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1563ce14880000
kernel config: https://syzkaller.appspot.com/x/.config?x=755695d26ad09807
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11106dec880000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9c8cf859a872/disk-b357fd1c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c1d370ace8a8/vmlinux-b357fd1c.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+15cb24...@syzkaller.appspotmail.com
loop0: detected capacity change from 0 to 8226
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
RIP: 0010:spin_unlock include/linux/spinlock.h:389 [inline]
RIP: 0010:writeback_single_inode+0x137/0x4c0 fs/fs-writeback.c:1728
Code: 8e 66 03 00 00 41 8b 5c 24 20 bf 01 00 00 00 89 de e8 ed 49 98 ff 83 fb 01 74 22 45 31 ff e8 20 4d 98 ff 4c 89 f7 e8 18 a8 9f <07> 44 89 f8 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 e8 01 4d
RSP: 0018:ffffc90003c7fa10 EFLAGS: 00010286
RAX: 0000000080000000 RBX: 0000000000000010 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 0000000000000004 RDI: 0000000000000001
RBP: ffff888071de4c10 R08: 0000000000000000 R09: ffff888071de4c9b
R10: ffffed100e3bc993 R11: 0000000000000000 R12: ffffc90003c7fa88
R13: ffff888071de4ce8 R14: ffff888071de4c98 R15: 0000000000000000
FS: 0000555556bc6300(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
Code: 48 c7 c2 c0 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 a8 00 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc5d57af98 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fb0e371181a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007ffc5d57afb0
RBP: 00007ffc5d57afb0 R08: 00007ffc5d57aff0 R09: 0000555556bc62c0
R10: 0000000000000000 R11: 0000000000000286 R12: 0000000000000004
R13: 00007ffc5d57aff0 R14: 0000000000000015 R15: 0000000020000db8
RIP: 0010:writeback_single_inode+0x137/0x4c0 fs/fs-writeback.c:1728
Code: 8e 66 03 00 00 41 8b 5c 24 20 bf 01 00 00 00 89 de e8 ed 49 98 ff 83 fb 01 74 22 45 31 ff e8 20 4d 98 ff 4c 89 f7 e8 18 a8 9f <07> 44 89 f8 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 e8 01 4d
RSP: 0018:ffffc90003c7fa10 EFLAGS: 00010286
RAX: 0000000080000000 RBX: 0000000000000010 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 0000000000000004 RDI: 0000000000000001
RBP: ffff888071de4c10 R08: 0000000000000000 R09: ffff888071de4c9b
R10: ffffed100e3bc993 R11: 0000000000000000 R12: ffffc90003c7fa88
R13: ffff888071de4ce8 R14: ffff888071de4c98 R15: 0000000000000000
FS: 0000555556bc6300(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
HEAD commit: b357fd1c2afc Merge tag 'usb-6.0-final' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1563ce14880000
kernel config: https://syzkaller.appspot.com/x/.config?x=755695d26ad09807
dashboard link: https://syzkaller.appspot.com/bug?extid=15cb24a539075fc4c472
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=155d3a82880000
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11106dec880000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9c8cf859a872/disk-b357fd1c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c1d370ace8a8/vmlinux-b357fd1c.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+15cb24...@syzkaller.appspotmail.com
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 3881 Comm: syz-executor338 Not tainted 6.0.0-rc7-syzkaller-00239-gb357fd1c2afc #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
RIP: 0010:spin_unlock include/linux/spinlock.h:389 [inline]
RIP: 0010:writeback_single_inode+0x137/0x4c0 fs/fs-writeback.c:1728
Code: 8e 66 03 00 00 41 8b 5c 24 20 bf 01 00 00 00 89 de e8 ed 49 98 ff 83 fb 01 74 22 45 31 ff e8 20 4d 98 ff 4c 89 f7 e8 18 a8 9f <07> 44 89 f8 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 e8 01 4d
RSP: 0018:ffffc90003c7fa10 EFLAGS: 00010286
RAX: 0000000080000000 RBX: 0000000000000010 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 0000000000000004 RDI: 0000000000000001
RBP: ffff888071de4c10 R08: 0000000000000000 R09: ffff888071de4c9b
R10: ffffed100e3bc993 R11: 0000000000000000 R12: ffffc90003c7fa88
R13: ffff888071de4ce8 R14: ffff888071de4c98 R15: 0000000000000000
FS: 0000555556bc6300(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020003580 CR3: 0000000074274000 CR4: 0000000000350ee0
Call Trace:
<TASK>
write_inode_now+0x16a/0x1e0 fs/fs-writeback.c:2723
iput_final fs/inode.c:1735 [inline]
iput.part.0+0x45b/0x810 fs/inode.c:1774
iput+0x58/0x70 fs/inode.c:1764
ntfs_fill_super+0x2e89/0x37f0 fs/ntfs3/super.c:1190
get_tree_bdev+0x440/0x760 fs/super.c:1323
vfs_get_tree+0x89/0x2f0 fs/super.c:1530
do_new_mount fs/namespace.c:3040 [inline]
path_mount+0x1326/0x1e20 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__x64_sys_mount+0x27f/0x300 fs/namespace.c:3568
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fb0e371181a
<TASK>
write_inode_now+0x16a/0x1e0 fs/fs-writeback.c:2723
iput_final fs/inode.c:1735 [inline]
iput.part.0+0x45b/0x810 fs/inode.c:1774
iput+0x58/0x70 fs/inode.c:1764
ntfs_fill_super+0x2e89/0x37f0 fs/ntfs3/super.c:1190
get_tree_bdev+0x440/0x760 fs/super.c:1323
vfs_get_tree+0x89/0x2f0 fs/super.c:1530
do_new_mount fs/namespace.c:3040 [inline]
path_mount+0x1326/0x1e20 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__x64_sys_mount+0x27f/0x300 fs/namespace.c:3568
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
Code: 48 c7 c2 c0 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 a8 00 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc5d57af98 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fb0e371181a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007ffc5d57afb0
RBP: 00007ffc5d57afb0 R08: 00007ffc5d57aff0 R09: 0000555556bc62c0
R10: 0000000000000000 R11: 0000000000000286 R12: 0000000000000004
R13: 00007ffc5d57aff0 R14: 0000000000000015 R15: 0000000020000db8
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:spin_unlock include/linux/spinlock.h:389 [inline]
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:writeback_single_inode+0x137/0x4c0 fs/fs-writeback.c:1728
Code: 8e 66 03 00 00 41 8b 5c 24 20 bf 01 00 00 00 89 de e8 ed 49 98 ff 83 fb 01 74 22 45 31 ff e8 20 4d 98 ff 4c 89 f7 e8 18 a8 9f <07> 44 89 f8 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 e8 01 4d
RSP: 0018:ffffc90003c7fa10 EFLAGS: 00010286
RAX: 0000000080000000 RBX: 0000000000000010 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 0000000000000004 RDI: 0000000000000001
RBP: ffff888071de4c10 R08: 0000000000000000 R09: ffff888071de4c9b
R10: ffffed100e3bc993 R11: 0000000000000000 R12: ffffc90003c7fa88
R13: ffff888071de4ce8 R14: ffff888071de4c98 R15: 0000000000000000
FS: 0000555556bc6300(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb0e3740230 CR3: 0000000074274000 CR4: 0000000000350ef0
syzbot
Dec 23, 2023, 12:18:12 AM12/23/23
to syzkall...@googlegroups.com
Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.
No recent activity, existing reproducers are no longer triggering the issue.
Reply all
Reply to author
Forward
0 new messages