[v5.15] kernel BUG in jbd2_cleanup_journal_tail
0 views
Skip to first unread message
syzbot
Sep 15, 2024, 7:09:30 PMSep 15
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 3a5928702e71 Linux 5.15.167
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14ee229f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=171882977b524c53
dashboard link: https://syzkaller.appspot.com/bug?extid=08247eaf130b8e3b3363
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/22ee27cb312d/disk-3a592870.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/90bf6a3e3d20/vmlinux-3a592870.xz
kernel image: https://storage.googleapis.com/syzbot-assets/096dd2c73ac3/Image-3a592870.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+08247e...@syzkaller.appspotmail.com
(syz.2.190,4703,0):ocfs2_check_volume:2429 ERROR: ocfs2 journal load failed! -5
(syz.2.190,4703,0):ocfs2_check_volume:2485 ERROR: status = -5
(syz.2.190,4703,0):ocfs2_mount_volume:1824 ERROR: status = -5
------------[ cut here ]------------
kernel BUG at fs/jbd2/checkpoint.c:333!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4703 Comm: syz.2.190 Not tainted 5.15.167-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : jbd2_cleanup_journal_tail+0x244/0x248 fs/jbd2/checkpoint.c:333
lr : jbd2_cleanup_journal_tail+0x244/0x248 fs/jbd2/checkpoint.c:333
sp : ffff800020446940
x29: ffff8000204469c0 x28: 0000000000000000 x27: 1fffe000194fc800
x26: 1ffff00004088d2e x25: 1ffff00004088d2c x24: dfff800000000000
x23: ffff700004088d28 x22: 0000000000000000 x21: ffff800020446960
x20: ffff800020446970 x19: ffff0000ca7e4000 x18: ffff8000204465c0
x17: 1fffe00036831b8e x16: ffff80000824ecc0 x15: 0000000000000005
x14: ffff80001713e500 x13: dfff800000000000 x12: 0000000000040000
x11: 000000000003ffff x10: ffff8000220ea000 x9 : 0000000000040000
x8 : ffff800008eec608 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000020 x4 : 0000000000000000 x3 : ffff800008305e14
x2 : 0000000000000001 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
jbd2_cleanup_journal_tail+0x244/0x248 fs/jbd2/checkpoint.c:333
jbd2_journal_flush+0x2ac/0xaa0 fs/jbd2/journal.c:2486
ocfs2_journal_shutdown+0x394/0xb84 fs/ocfs2/journal.c:1020
ocfs2_mount_volume+0x12d8/0x150c fs/ocfs2/super.c:1845
ocfs2_fill_super+0x2a30/0x498c fs/ocfs2/super.c:1083
mount_bdev+0x274/0x370 fs/super.c:1398
ocfs2_mount+0x44/0x58 fs/ocfs2/super.c:1187
legacy_get_tree+0xd4/0x16c fs/fs_context.c:611
vfs_get_tree+0x90/0x274 fs/super.c:1528
do_new_mount+0x278/0x8fc fs/namespace.c:3005
path_mount+0x594/0x101c fs/namespace.c:3335
do_mount fs/namespace.c:3348 [inline]
__do_sys_mount fs/namespace.c:3556 [inline]
__se_sys_mount fs/namespace.c:3533 [inline]
__arm64_sys_mount+0x510/0x5e0 fs/namespace.c:3533
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: 97e7a71a 17ffffd7 95c0f55e 97d7662d (d4210000)
---[ end trace 5c81aab49a427e9d ]---
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot found the following issue on:
HEAD commit: 3a5928702e71 Linux 5.15.167
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14ee229f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=171882977b524c53
dashboard link: https://syzkaller.appspot.com/bug?extid=08247eaf130b8e3b3363
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/22ee27cb312d/disk-3a592870.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/90bf6a3e3d20/vmlinux-3a592870.xz
kernel image: https://storage.googleapis.com/syzbot-assets/096dd2c73ac3/Image-3a592870.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+08247e...@syzkaller.appspotmail.com
(syz.2.190,4703,0):ocfs2_check_volume:2429 ERROR: ocfs2 journal load failed! -5
(syz.2.190,4703,0):ocfs2_check_volume:2485 ERROR: status = -5
(syz.2.190,4703,0):ocfs2_mount_volume:1824 ERROR: status = -5
------------[ cut here ]------------
kernel BUG at fs/jbd2/checkpoint.c:333!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4703 Comm: syz.2.190 Not tainted 5.15.167-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : jbd2_cleanup_journal_tail+0x244/0x248 fs/jbd2/checkpoint.c:333
lr : jbd2_cleanup_journal_tail+0x244/0x248 fs/jbd2/checkpoint.c:333
sp : ffff800020446940
x29: ffff8000204469c0 x28: 0000000000000000 x27: 1fffe000194fc800
x26: 1ffff00004088d2e x25: 1ffff00004088d2c x24: dfff800000000000
x23: ffff700004088d28 x22: 0000000000000000 x21: ffff800020446960
x20: ffff800020446970 x19: ffff0000ca7e4000 x18: ffff8000204465c0
x17: 1fffe00036831b8e x16: ffff80000824ecc0 x15: 0000000000000005
x14: ffff80001713e500 x13: dfff800000000000 x12: 0000000000040000
x11: 000000000003ffff x10: ffff8000220ea000 x9 : 0000000000040000
x8 : ffff800008eec608 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000020 x4 : 0000000000000000 x3 : ffff800008305e14
x2 : 0000000000000001 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
jbd2_cleanup_journal_tail+0x244/0x248 fs/jbd2/checkpoint.c:333
jbd2_journal_flush+0x2ac/0xaa0 fs/jbd2/journal.c:2486
ocfs2_journal_shutdown+0x394/0xb84 fs/ocfs2/journal.c:1020
ocfs2_mount_volume+0x12d8/0x150c fs/ocfs2/super.c:1845
ocfs2_fill_super+0x2a30/0x498c fs/ocfs2/super.c:1083
mount_bdev+0x274/0x370 fs/super.c:1398
ocfs2_mount+0x44/0x58 fs/ocfs2/super.c:1187
legacy_get_tree+0xd4/0x16c fs/fs_context.c:611
vfs_get_tree+0x90/0x274 fs/super.c:1528
do_new_mount+0x278/0x8fc fs/namespace.c:3005
path_mount+0x594/0x101c fs/namespace.c:3335
do_mount fs/namespace.c:3348 [inline]
__do_sys_mount fs/namespace.c:3556 [inline]
__se_sys_mount fs/namespace.c:3533 [inline]
__arm64_sys_mount+0x510/0x5e0 fs/namespace.c:3533
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: 97e7a71a 17ffffd7 95c0f55e 97d7662d (d4210000)
---[ end trace 5c81aab49a427e9d ]---
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot
Sep 15, 2024, 7:20:29 PMSep 15
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 3a5928702e71 Linux 5.15.167
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=174dc8a9980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13be229f980000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/22ee27cb312d/disk-3a592870.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/90bf6a3e3d20/vmlinux-3a592870.xz
kernel image: https://storage.googleapis.com/syzbot-assets/096dd2c73ac3/Image-3a592870.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/3bef3bb52322/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+08247e...@syzkaller.appspotmail.com
(syz-executor157,4021,1):ocfs2_check_volume:2429 ERROR: ocfs2 journal load failed! -5
(syz-executor157,4021,1):ocfs2_check_volume:2485 ERROR: status = -5
(syz-executor157,4021,1):ocfs2_mount_volume:1824 ERROR: status = -5
x29: ffff80001fe669c0 x28: 0000000000000000 x27: 1fffe00019655c00
x26: 1ffff00003fccd2e x25: 1ffff00003fccd2c x24: dfff800000000000
x23: ffff700003fccd28 x22: 0000000000000000 x21: ffff80001fe66960
x20: ffff80001fe66970 x19: ffff0000cb2ae000 x18: ffff80001fe665c0
x17: 1fffe00036835d8e x16: ffff80000824ecc0 x15: 000000000000bbd3
x14: ffff80001713e500 x13: dfff800000000000 x12: 0000000000000001
x11: 0000000000000000 x10: 0000000000000000 x9 : ffff0000cb6cd1c0
---[ end trace 418bfbff431403d6 ]---
---
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: 3a5928702e71 Linux 5.15.167
git tree: linux-5.15.y
kernel config: https://syzkaller.appspot.com/x/.config?x=171882977b524c53
dashboard link: https://syzkaller.appspot.com/bug?extid=08247eaf130b8e3b3363
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10cdc8a9980000
dashboard link: https://syzkaller.appspot.com/bug?extid=08247eaf130b8e3b3363
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13be229f980000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/22ee27cb312d/disk-3a592870.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/90bf6a3e3d20/vmlinux-3a592870.xz
kernel image: https://storage.googleapis.com/syzbot-assets/096dd2c73ac3/Image-3a592870.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+08247e...@syzkaller.appspotmail.com
(syz-executor157,4021,1):ocfs2_check_volume:2485 ERROR: status = -5
(syz-executor157,4021,1):ocfs2_mount_volume:1824 ERROR: status = -5
------------[ cut here ]------------
kernel BUG at fs/jbd2/checkpoint.c:333!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4021 Comm: syz-executor157 Not tainted 5.15.167-syzkaller #0
kernel BUG at fs/jbd2/checkpoint.c:333!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : jbd2_cleanup_journal_tail+0x244/0x248 fs/jbd2/checkpoint.c:333
lr : jbd2_cleanup_journal_tail+0x244/0x248 fs/jbd2/checkpoint.c:333
sp : ffff80001fe66940
lr : jbd2_cleanup_journal_tail+0x244/0x248 fs/jbd2/checkpoint.c:333
x29: ffff80001fe669c0 x28: 0000000000000000 x27: 1fffe00019655c00
x26: 1ffff00003fccd2e x25: 1ffff00003fccd2c x24: dfff800000000000
x23: ffff700003fccd28 x22: 0000000000000000 x21: ffff80001fe66960
x20: ffff80001fe66970 x19: ffff0000cb2ae000 x18: ffff80001fe665c0
x17: 1fffe00036835d8e x16: ffff80000824ecc0 x15: 000000000000bbd3
x14: ffff80001713e500 x13: dfff800000000000 x12: 0000000000000001
x11: 0000000000000000 x10: 0000000000000000 x9 : ffff0000cb6cd1c0
---
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
Sep 16, 2024, 10:30:29 PMSep 16
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 5f55cad62cc9 Linux 6.1.110
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=156c68a9980000
kernel config: https://syzkaller.appspot.com/x/.config?x=625d3d5479b9ea13
dashboard link: https://syzkaller.appspot.com/bug?extid=087b1b3234832ee66463
disk image: https://storage.googleapis.com/syzbot-assets/406d4fabf0c5/disk-5f55cad6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/abc54e64f4c6/vmlinux-5f55cad6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5d3b04a9f829/Image-5f55cad6.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+087b1b...@syzkaller.appspotmail.com
(syz.2.63,4638,1):ocfs2_check_volume:2481 ERROR: status = -5
(syz.2.63,4638,1):ocfs2_mount_volume:1821 ERROR: status = -5
x29: ffff800023ae6a60 x28: 0000000000000000 x27: 1fffe0001baf5400
x26: 1ffff0000475cd42 x25: 1ffff0000475cd40 x24: dfff800000000000
x23: ffff70000475cd3c x22: 0000000000000000 x21: ffff800023ae6a00
x20: ffff800023ae6a10 x19: ffff0000dd7aa000 x18: ffff800023ae6680
x17: ffff800018aa4000 x16: ffff80000825fff8 x15: ffff800018589f80
x14: ffff0000ce728a78 x13: dfff800000000000 x12: 0000000000040000
x11: 000000000003ffff x10: ffff800022b82000 x9 : ffff800008fb7d44
x8 : 0000000000040000 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000020 x4 : 0000000000000000 x3 : ffff80000831e8c8
ocfs2_journal_shutdown+0x3dc/0xc8c fs/ocfs2/journal.c:1048
ocfs2_mount_volume+0x12d8/0x1508 fs/ocfs2/super.c:1842
ocfs2_fill_super+0x3adc/0x4a0c fs/ocfs2/super.c:1082
mount_bdev+0x274/0x370 fs/super.c:1443
ocfs2_mount+0x44/0x58 fs/ocfs2/super.c:1186
legacy_get_tree+0xd4/0x16c fs/fs_context.c:632
vfs_get_tree+0x90/0x274 fs/super.c:1573
do_new_mount+0x278/0x8fc fs/namespace.c:3051
path_mount+0x590/0xe5c fs/namespace.c:3381
do_mount fs/namespace.c:3394 [inline]
__do_sys_mount fs/namespace.c:3602 [inline]
__se_sys_mount fs/namespace.c:3579 [inline]
__arm64_sys_mount+0x45c/0x594 fs/namespace.c:3579
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
Code: 97e71db7 17ffffd7 95bdc335 97d50d2b (d4210000)
---[ end trace 0000000000000000 ]---
syzbot found the following issue on:
HEAD commit: 5f55cad62cc9 Linux 6.1.110
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=156c68a9980000
kernel config: https://syzkaller.appspot.com/x/.config?x=625d3d5479b9ea13
dashboard link: https://syzkaller.appspot.com/bug?extid=087b1b3234832ee66463
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/406d4fabf0c5/disk-5f55cad6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/abc54e64f4c6/vmlinux-5f55cad6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5d3b04a9f829/Image-5f55cad6.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
(syz.2.63,4638,1):ocfs2_check_volume:2481 ERROR: status = -5
(syz.2.63,4638,1):ocfs2_mount_volume:1821 ERROR: status = -5
------------[ cut here ]------------
kernel BUG at fs/jbd2/checkpoint.c:333!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4638 Comm: syz.2.63 Not tainted 6.1.110-syzkaller #0
kernel BUG at fs/jbd2/checkpoint.c:333!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : jbd2_cleanup_journal_tail+0x244/0x248 fs/jbd2/checkpoint.c:333
lr : jbd2_cleanup_journal_tail+0x244/0x248 fs/jbd2/checkpoint.c:333
sp : ffff800023ae69e0
lr : jbd2_cleanup_journal_tail+0x244/0x248 fs/jbd2/checkpoint.c:333
x29: ffff800023ae6a60 x28: 0000000000000000 x27: 1fffe0001baf5400
x26: 1ffff0000475cd42 x25: 1ffff0000475cd40 x24: dfff800000000000
x23: ffff70000475cd3c x22: 0000000000000000 x21: ffff800023ae6a00
x20: ffff800023ae6a10 x19: ffff0000dd7aa000 x18: ffff800023ae6680
x17: ffff800018aa4000 x16: ffff80000825fff8 x15: ffff800018589f80
x14: ffff0000ce728a78 x13: dfff800000000000 x12: 0000000000040000
x11: 000000000003ffff x10: ffff800022b82000 x9 : ffff800008fb7d44
x8 : 0000000000040000 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000020 x4 : 0000000000000000 x3 : ffff80000831e8c8
x2 : 0000000000000001 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
jbd2_cleanup_journal_tail+0x244/0x248 fs/jbd2/checkpoint.c:333
jbd2_journal_flush+0x2ac/0xb2c fs/jbd2/journal.c:2489
Call trace:
jbd2_cleanup_journal_tail+0x244/0x248 fs/jbd2/checkpoint.c:333
ocfs2_journal_shutdown+0x3dc/0xc8c fs/ocfs2/journal.c:1048
ocfs2_mount_volume+0x12d8/0x1508 fs/ocfs2/super.c:1842
ocfs2_fill_super+0x3adc/0x4a0c fs/ocfs2/super.c:1082
mount_bdev+0x274/0x370 fs/super.c:1443
ocfs2_mount+0x44/0x58 fs/ocfs2/super.c:1186
legacy_get_tree+0xd4/0x16c fs/fs_context.c:632
vfs_get_tree+0x90/0x274 fs/super.c:1573
do_new_mount+0x278/0x8fc fs/namespace.c:3051
path_mount+0x590/0xe5c fs/namespace.c:3381
do_mount fs/namespace.c:3394 [inline]
__do_sys_mount fs/namespace.c:3602 [inline]
__se_sys_mount fs/namespace.c:3579 [inline]
__arm64_sys_mount+0x45c/0x594 fs/namespace.c:3579
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
Code: 97e71db7 17ffffd7 95bdc335 97d50d2b (d4210000)
---[ end trace 0000000000000000 ]---
syzbot
Sep 17, 2024, 11:51:27 AMSep 17
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 5f55cad62cc9 Linux 6.1.110
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12213500580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16213500580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/406d4fabf0c5/disk-5f55cad6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/abc54e64f4c6/vmlinux-5f55cad6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5d3b04a9f829/Image-5f55cad6.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/28107a72b3c8/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+087b1b...@syzkaller.appspotmail.com
(syz-executor257,4294,1):ocfs2_check_volume:2425 ERROR: ocfs2 journal load failed! -5
(syz-executor257,4294,1):ocfs2_check_volume:2481 ERROR: status = -5
(syz-executor257,4294,1):ocfs2_mount_volume:1821 ERROR: status = -5
x29: ffff800020fe6a60 x28: 0000000000000000 x27: 1fffe00019d9c400
x26: 1ffff000041fcd42 x25: 1ffff000041fcd40 x24: dfff800000000000
x23: ffff7000041fcd3c x22: 0000000000000000 x21: ffff800020fe6a00
x20: ffff800020fe6a10 x19: ffff0000cece2000 x18: ffff800020fe6680
x11: 0000000000ff0100 x10: 0000000000000000 x9 : ffff800008fb7d44
x8 : ffff0000c8ad0000 x7 : 0000000000000000 x6 : 0000000000000000
HEAD commit: 5f55cad62cc9 Linux 6.1.110
git tree: linux-6.1.y
kernel config: https://syzkaller.appspot.com/x/.config?x=625d3d5479b9ea13
dashboard link: https://syzkaller.appspot.com/bug?extid=087b1b3234832ee66463
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=102be207980000
dashboard link: https://syzkaller.appspot.com/bug?extid=087b1b3234832ee66463
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16213500580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/406d4fabf0c5/disk-5f55cad6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/abc54e64f4c6/vmlinux-5f55cad6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5d3b04a9f829/Image-5f55cad6.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+087b1b...@syzkaller.appspotmail.com
(syz-executor257,4294,1):ocfs2_check_volume:2481 ERROR: status = -5
(syz-executor257,4294,1):ocfs2_mount_volume:1821 ERROR: status = -5
------------[ cut here ]------------
kernel BUG at fs/jbd2/checkpoint.c:333!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4294 Comm: syz-executor257 Not tainted 6.1.110-syzkaller #0
kernel BUG at fs/jbd2/checkpoint.c:333!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : jbd2_cleanup_journal_tail+0x244/0x248 fs/jbd2/checkpoint.c:333
lr : jbd2_cleanup_journal_tail+0x244/0x248 fs/jbd2/checkpoint.c:333
sp : ffff800020fe69e0
lr : jbd2_cleanup_journal_tail+0x244/0x248 fs/jbd2/checkpoint.c:333
x29: ffff800020fe6a60 x28: 0000000000000000 x27: 1fffe00019d9c400
x26: 1ffff000041fcd42 x25: 1ffff000041fcd40 x24: dfff800000000000
x23: ffff7000041fcd3c x22: 0000000000000000 x21: ffff800020fe6a00
x20: ffff800020fe6a10 x19: ffff0000cece2000 x18: ffff800020fe6680
x17: ffff800018aa4000 x16: ffff80000825fff8 x15: ffff800018589f80
x14: ffff0000c8ad0a78 x13: dfff800000000000 x12: 0000000000000001
x11: 0000000000ff0100 x10: 0000000000000000 x9 : ffff800008fb7d44
x8 : ffff0000c8ad0000 x7 : 0000000000000000 x6 : 0000000000000000
Reply all
Reply to author
Forward
0 new messages