[v6.1] kernel BUG in hfs_write_inode
0 views
Skip to first unread message
syzbot
Apr 4, 2023, 3:01:47 AM4/4/23
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 3b29299e5f60 Linux 6.1.22
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12c485f1c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=4a782518325cb082
dashboard link: https://syzkaller.appspot.com/bug?extid=c5103cae7270551db1e6
compiler: Debian clang version 15.0.7, 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/syzbot-assets/f6cdeb0f8946/disk-3b29299e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cc5e0da6e9ab/vmlinux-3b29299e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9e31f151a6a5/bzImage-3b29299e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c5103c...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/hfs/inode.c:446!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 1060 Comm: kworker/u4:5 Not tainted 6.1.22-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: writeback wb_workfn (flush-7:2)
RIP: 0010:hfs_write_inode+0xeb0/0xec0 fs/hfs/inode.c:446
Code: ff e9 88 fb ff ff 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 9d fb ff ff e8 4f cd 7f ff e9 93 fb ff ff e8 d5 e9 1d 08 e8 c0 ac 29 ff <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 41 57 41 56 41 54
RSP: 0018:ffffc90004c5f360 EFLAGS: 00010293
RAX: ffffffff825fe0e0 RBX: 0000000000000005 RCX: ffff8880201c9d40
RDX: 0000000000000000 RSI: ffffffff8d1187a0 RDI: 0000000000000005
RBP: ffffc90004c5f4f0 R08: 0000000000000007 R09: ffffffff825fd38a
R10: 0000000000000003 R11: ffff8880201c9d40 R12: 1ffff9200098be70
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff888075805c58
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020081000 CR3: 000000007cac0000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
write_inode fs/fs-writeback.c:1440 [inline]
__writeback_single_inode+0x67d/0x11e0 fs/fs-writeback.c:1652
writeback_sb_inodes+0xc21/0x1ac0 fs/fs-writeback.c:1878
wb_writeback+0x49d/0xe10 fs/fs-writeback.c:2052
wb_do_writeback fs/fs-writeback.c:2195 [inline]
wb_workfn+0x427/0x1020 fs/fs-writeback.c:2235
process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2289
worker_thread+0xa5f/0x1210 kernel/workqueue.c:2436
kthread+0x268/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:hfs_write_inode+0xeb0/0xec0 fs/hfs/inode.c:446
Code: ff e9 88 fb ff ff 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 9d fb ff ff e8 4f cd 7f ff e9 93 fb ff ff e8 d5 e9 1d 08 e8 c0 ac 29 ff <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 41 57 41 56 41 54
RSP: 0018:ffffc90004c5f360 EFLAGS: 00010293
RAX: ffffffff825fe0e0 RBX: 0000000000000005 RCX: ffff8880201c9d40
RDX: 0000000000000000 RSI: ffffffff8d1187a0 RDI: 0000000000000005
RBP: ffffc90004c5f4f0 R08: 0000000000000007 R09: ffffffff825fd38a
R10: 0000000000000003 R11: ffff8880201c9d40 R12: 1ffff9200098be70
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff888075805c58
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fff650bdbd8 CR3: 0000000085aa7000 CR4: 00000000003506f0
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: 3b29299e5f60 Linux 6.1.22
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12c485f1c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=4a782518325cb082
dashboard link: https://syzkaller.appspot.com/bug?extid=c5103cae7270551db1e6
compiler: Debian clang version 15.0.7, 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/syzbot-assets/f6cdeb0f8946/disk-3b29299e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cc5e0da6e9ab/vmlinux-3b29299e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9e31f151a6a5/bzImage-3b29299e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c5103c...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/hfs/inode.c:446!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 1060 Comm: kworker/u4:5 Not tainted 6.1.22-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: writeback wb_workfn (flush-7:2)
RIP: 0010:hfs_write_inode+0xeb0/0xec0 fs/hfs/inode.c:446
Code: ff e9 88 fb ff ff 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 9d fb ff ff e8 4f cd 7f ff e9 93 fb ff ff e8 d5 e9 1d 08 e8 c0 ac 29 ff <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 41 57 41 56 41 54
RSP: 0018:ffffc90004c5f360 EFLAGS: 00010293
RAX: ffffffff825fe0e0 RBX: 0000000000000005 RCX: ffff8880201c9d40
RDX: 0000000000000000 RSI: ffffffff8d1187a0 RDI: 0000000000000005
RBP: ffffc90004c5f4f0 R08: 0000000000000007 R09: ffffffff825fd38a
R10: 0000000000000003 R11: ffff8880201c9d40 R12: 1ffff9200098be70
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff888075805c58
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020081000 CR3: 000000007cac0000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
write_inode fs/fs-writeback.c:1440 [inline]
__writeback_single_inode+0x67d/0x11e0 fs/fs-writeback.c:1652
writeback_sb_inodes+0xc21/0x1ac0 fs/fs-writeback.c:1878
wb_writeback+0x49d/0xe10 fs/fs-writeback.c:2052
wb_do_writeback fs/fs-writeback.c:2195 [inline]
wb_workfn+0x427/0x1020 fs/fs-writeback.c:2235
process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2289
worker_thread+0xa5f/0x1210 kernel/workqueue.c:2436
kthread+0x268/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:hfs_write_inode+0xeb0/0xec0 fs/hfs/inode.c:446
Code: ff e9 88 fb ff ff 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 9d fb ff ff e8 4f cd 7f ff e9 93 fb ff ff e8 d5 e9 1d 08 e8 c0 ac 29 ff <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 41 57 41 56 41 54
RSP: 0018:ffffc90004c5f360 EFLAGS: 00010293
RAX: ffffffff825fe0e0 RBX: 0000000000000005 RCX: ffff8880201c9d40
RDX: 0000000000000000 RSI: ffffffff8d1187a0 RDI: 0000000000000005
RBP: ffffc90004c5f4f0 R08: 0000000000000007 R09: ffffffff825fd38a
R10: 0000000000000003 R11: ffff8880201c9d40 R12: 1ffff9200098be70
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff888075805c58
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fff650bdbd8 CR3: 0000000085aa7000 CR4: 00000000003506f0
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
Apr 10, 2023, 9:50:47 AM4/10/23
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: d86dfc4d95cd Linux 5.15.106
syzbot found the following issue on:
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13ac9a4bc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=dca379fe384dda80
dashboard link: https://syzkaller.appspot.com/bug?extid=2b311dee7c3dadfc1a7e
compiler: Debian clang version 15.0.7, 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/syzbot-assets/2c159eb4fcae/disk-d86dfc4d.raw.xz
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
vmlinux: https://storage.googleapis.com/syzbot-assets/5f50187f87c7/vmlinux-d86dfc4d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f787f3f09c09/bzImage-d86dfc4d.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
------------[ cut here ]------------
kernel BUG at fs/hfs/inode.c:444!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 1142 Comm: kworker/u4:4 Not tainted 5.15.106-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
Workqueue: writeback wb_workfn (flush-7:2)
RIP: 0010:hfs_write_inode+0xeb0/0xec0 fs/hfs/inode.c:444
Code: ff e9 88 fb ff ff 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 9d fb ff ff e8 4f 54 86 ff e9 93 fb ff ff e8 a5 38 d4 07 e8 00 0c 3d ff <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 41 57 41 56 41 54
RSP: 0018:ffffc9000552f360 EFLAGS: 00010293
RAX: ffffffff8242aeb0 RBX: 0000000000000005 RCX: ffff88801cda1d00
RDX: 0000000000000000 RSI: ffffffff8cadfb80 RDI: 0000000000000005
RBP: ffffc9000552f4f0 R08: 0000000000000007 R09: ffffffff8242a15a
R10: 0000000000000003 R11: ffff88801cda1d00 R12: 1ffff92000aa5e70
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff88807ea21b58
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c01f5b1000 CR3: 00000000676be000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
write_inode fs/fs-writeback.c:1475 [inline]
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__writeback_single_inode+0x644/0xe30 fs/fs-writeback.c:1680
writeback_sb_inodes+0xbf0/0x1a50 fs/fs-writeback.c:1905
wb_writeback+0x451/0xc50 fs/fs-writeback.c:2079
wb_do_writeback fs/fs-writeback.c:2222 [inline]
wb_workfn+0x46c/0x1130 fs/fs-writeback.c:2263
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2306
worker_thread+0xaca/0x1280 kernel/workqueue.c:2453
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
Modules linked in:
---[ end trace 0a5ef14d1c3cb68f ]---
RIP: 0010:hfs_write_inode+0xeb0/0xec0 fs/hfs/inode.c:444
Code: ff e9 88 fb ff ff 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 9d fb ff ff e8 4f 54 86 ff e9 93 fb ff ff e8 a5 38 d4 07 e8 00 0c 3d ff <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 41 57 41 56 41 54
RSP: 0018:ffffc9000552f360 EFLAGS: 00010293
RAX: ffffffff8242aeb0 RBX: 0000000000000005 RCX: ffff88801cda1d00
RDX: 0000000000000000 RSI: ffffffff8cadfb80 RDI: 0000000000000005
RBP: ffffc9000552f4f0 R08: 0000000000000007 R09: ffffffff8242a15a
R10: 0000000000000003 R11: ffff88801cda1d00 R12: 1ffff92000aa5e70
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff88807ea21b58
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f226eaa1d38 CR3: 000000001cc81000 CR4: 00000000003526e0
syzbot
May 22, 2023, 3:40:54 AM5/22/23
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 9d6bde853685 Linux 5.15.112
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=161a3046280000
kernel config: https://syzkaller.appspot.com/x/.config?x=508f7a387ef8f82b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1189bd91280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12e548de280000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a8ab2bd416bb/disk-9d6bde85.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c358e3d58bb2/vmlinux-9d6bde85.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c82319bbaeb8/Image-9d6bde85.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/b48108396e0e/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2b311d...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/hfs/inode.c:444!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 148 Comm: kworker/u4:2 Not tainted 5.15.112-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
Workqueue: writeback wb_workfn (flush-7:0)
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : hfs_write_inode+0xc18/0xc1c fs/hfs/inode.c:444
lr : hfs_write_inode+0xc18/0xc1c fs/hfs/inode.c:444
sp : ffff80001a3b71a0
x29: ffff80001a3b7300 x28: dfff800000000000 x27: ffff700003476e38
x26: ffff80001a3b71c0 x25: ffff8000148cd310 x24: 0000000000000001
x23: ffff800011bcece0 x22: 0000000000000005 x21: ffff0000d7802ed8
x20: ffff80001a3b7240 x19: ffff80001a3b71e0 x18: 0000000000000000
x17: ff80800008fd9f0c x16: 0000000000000000 x15: ffff800008fd9f0c
x14: 0000000000000004 x13: ffffffffffffffff x12: 0000000000000000
x11: ff80800008fda9b8 x10: 0000000000000000 x9 : ffff800008fda9b8
x8 : ffff0000c2bfb680 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000030
x2 : 0000000000000008 x1 : ffff800014c5aa00 x0 : 0000000000000005
Call trace:
hfs_write_inode+0xc18/0xc1c fs/hfs/inode.c:444
write_inode fs/fs-writeback.c:1478 [inline]
__writeback_single_inode+0x584/0x13a4 fs/fs-writeback.c:1683
writeback_sb_inodes+0x94c/0x1620 fs/fs-writeback.c:1908
wb_writeback+0x3fc/0xfc8 fs/fs-writeback.c:2082
wb_do_writeback fs/fs-writeback.c:2225 [inline]
wb_workfn+0x3a4/0x1070 fs/fs-writeback.c:2266
process_one_work+0x790/0x11b8 kernel/workqueue.c:2307
worker_thread+0x910/0x1034 kernel/workqueue.c:2454
kthread+0x37c/0x45c kernel/kthread.c:319
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
Code: aa1803e0 97e3afa4 17ffff00 97d39d2b (d4210000)
---[ end trace 4f0a31eb9a83e222 ]---
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
HEAD commit: 9d6bde853685 Linux 5.15.112
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=161a3046280000
kernel config: https://syzkaller.appspot.com/x/.config?x=508f7a387ef8f82b
dashboard link: https://syzkaller.appspot.com/bug?extid=2b311dee7c3dadfc1a7e
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1189bd91280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12e548de280000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a8ab2bd416bb/disk-9d6bde85.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c358e3d58bb2/vmlinux-9d6bde85.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c82319bbaeb8/Image-9d6bde85.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/b48108396e0e/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2b311d...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/hfs/inode.c:444!
Modules linked in:
CPU: 0 PID: 148 Comm: kworker/u4:2 Not tainted 5.15.112-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
Workqueue: writeback wb_workfn (flush-7:0)
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : hfs_write_inode+0xc18/0xc1c fs/hfs/inode.c:444
lr : hfs_write_inode+0xc18/0xc1c fs/hfs/inode.c:444
sp : ffff80001a3b71a0
x29: ffff80001a3b7300 x28: dfff800000000000 x27: ffff700003476e38
x26: ffff80001a3b71c0 x25: ffff8000148cd310 x24: 0000000000000001
x23: ffff800011bcece0 x22: 0000000000000005 x21: ffff0000d7802ed8
x20: ffff80001a3b7240 x19: ffff80001a3b71e0 x18: 0000000000000000
x17: ff80800008fd9f0c x16: 0000000000000000 x15: ffff800008fd9f0c
x14: 0000000000000004 x13: ffffffffffffffff x12: 0000000000000000
x11: ff80800008fda9b8 x10: 0000000000000000 x9 : ffff800008fda9b8
x8 : ffff0000c2bfb680 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000030
x2 : 0000000000000008 x1 : ffff800014c5aa00 x0 : 0000000000000005
Call trace:
hfs_write_inode+0xc18/0xc1c fs/hfs/inode.c:444
write_inode fs/fs-writeback.c:1478 [inline]
__writeback_single_inode+0x584/0x13a4 fs/fs-writeback.c:1683
writeback_sb_inodes+0x94c/0x1620 fs/fs-writeback.c:1908
wb_writeback+0x3fc/0xfc8 fs/fs-writeback.c:2082
wb_do_writeback fs/fs-writeback.c:2225 [inline]
wb_workfn+0x3a4/0x1070 fs/fs-writeback.c:2266
process_one_work+0x790/0x11b8 kernel/workqueue.c:2307
worker_thread+0x910/0x1034 kernel/workqueue.c:2454
kthread+0x37c/0x45c kernel/kthread.c:319
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
Code: aa1803e0 97e3afa4 17ffff00 97d39d2b (d4210000)
---[ end trace 4f0a31eb9a83e222 ]---
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
syzbot
May 22, 2023, 4:09:01 AM5/22/23
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: fa74641fb6b9 Linux 6.1.29
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=156471d9280000
kernel config: https://syzkaller.appspot.com/x/.config?x=7454aa89ac475d7b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15e0e629280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=102ea061280000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/53e4da6b145c/disk-fa74641f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/adeb1a2cfa86/vmlinux-fa74641f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c976f1155d08/Image-fa74641f.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/1a1b4b313caa/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c5103c...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/hfs/inode.c:446!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 55 Comm: kworker/u4:3 Not tainted 6.1.29-syzkaller #0
lr : hfs_write_inode+0xc18/0xc1c fs/hfs/inode.c:446
sp : ffff80001ca07180
x29: ffff80001ca072e0 x28: dfff800000000000 x27: ffff700003940e34
x26: ffff80001ca071a0 x25: ffff80001559d360 x24: 0000000000000001
x23: ffff800012397e80 x22: 0000000000000005 x21: ffff0000ddabaed8
x20: ffff80001ca07220 x19: ffff80001ca071c0 x18: ffff80001ca06a60
x17: ffff8000090a71c8 x16: 0000000000000000 x15: 0000000000000000
x14: 0000000000000000 x13: 0000000000000004 x12: ffff0000c49e9bc0
x11: ff808000090a74ec x10: 0000000000000000 x9 : ffff8000090a74ec
x8 : ffff0000c49e9bc0 x7 : 0000000000000000 x6 : 0000000000000000
Call trace:
hfs_write_inode+0xc18/0xc1c fs/hfs/inode.c:446
write_inode fs/fs-writeback.c:1443 [inline]
__writeback_single_inode+0x614/0x1770 fs/fs-writeback.c:1655
writeback_sb_inodes+0x978/0x16c0 fs/fs-writeback.c:1881
wb_writeback+0x414/0x1130 fs/fs-writeback.c:2055
wb_do_writeback fs/fs-writeback.c:2198 [inline]
wb_workfn+0x3a8/0x1034 fs/fs-writeback.c:2238
process_one_work+0x7ac/0x1404 kernel/workqueue.c:2289
worker_thread+0x8e4/0xfec kernel/workqueue.c:2436
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
Code: aa1803e0 97e319c6 17ffff00 97d14eae (d4210000)
HEAD commit: fa74641fb6b9 Linux 6.1.29
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=156471d9280000
kernel config: https://syzkaller.appspot.com/x/.config?x=7454aa89ac475d7b
dashboard link: https://syzkaller.appspot.com/bug?extid=c5103cae7270551db1e6
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15e0e629280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=102ea061280000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/53e4da6b145c/disk-fa74641f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/adeb1a2cfa86/vmlinux-fa74641f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c976f1155d08/Image-fa74641f.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/1a1b4b313caa/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c5103c...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/hfs/inode.c:446!
Modules linked in:
CPU: 0 PID: 55 Comm: kworker/u4:3 Not tainted 6.1.29-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
Workqueue: writeback wb_workfn (flush-7:0)
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : hfs_write_inode+0xc18/0xc1c fs/hfs/inode.c:446
Workqueue: writeback wb_workfn (flush-7:0)
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
lr : hfs_write_inode+0xc18/0xc1c fs/hfs/inode.c:446
sp : ffff80001ca07180
x29: ffff80001ca072e0 x28: dfff800000000000 x27: ffff700003940e34
x26: ffff80001ca071a0 x25: ffff80001559d360 x24: 0000000000000001
x23: ffff800012397e80 x22: 0000000000000005 x21: ffff0000ddabaed8
x20: ffff80001ca07220 x19: ffff80001ca071c0 x18: ffff80001ca06a60
x17: ffff8000090a71c8 x16: 0000000000000000 x15: 0000000000000000
x14: 0000000000000000 x13: 0000000000000004 x12: ffff0000c49e9bc0
x11: ff808000090a74ec x10: 0000000000000000 x9 : ffff8000090a74ec
x8 : ffff0000c49e9bc0 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000030
x2 : 0000000000000008 x1 : ffff800015953b40 x0 : 0000000000000005
Call trace:
hfs_write_inode+0xc18/0xc1c fs/hfs/inode.c:446
write_inode fs/fs-writeback.c:1443 [inline]
__writeback_single_inode+0x614/0x1770 fs/fs-writeback.c:1655
writeback_sb_inodes+0x978/0x16c0 fs/fs-writeback.c:1881
wb_writeback+0x414/0x1130 fs/fs-writeback.c:2055
wb_do_writeback fs/fs-writeback.c:2198 [inline]
wb_workfn+0x3a8/0x1034 fs/fs-writeback.c:2238
process_one_work+0x7ac/0x1404 kernel/workqueue.c:2289
worker_thread+0x8e4/0xfec kernel/workqueue.c:2436
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
Code: aa1803e0 97e319c6 17ffff00 97d14eae (d4210000)
---[ end trace 0000000000000000 ]---
Reply all
Reply to author
Forward
0 new messages