[moderation] [ext4?] general protection fault in jbd2_journal_dirty_metadata
2 views
Skip to first unread message
syzbot
Apr 22, 2025, 7:29:29 PM4/22/25
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 6fea5fabd332 Merge tag 'mm-hotfixes-stable-2025-04-19-21-2..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=150feccc580000
kernel config: https://syzkaller.appspot.com/x/.config?x=68d9f79fc685cd4
dashboard link: https://syzkaller.appspot.com/bug?extid=d066dd4ecc8199610806
compiler: Debian clang version 15.0.6, Debian LLD 15.0.6
CC: [ja...@suse.com linux...@vger.kernel.org linux-...@vger.kernel.org ty...@mit.edu]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-6fea5fab.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/196af7f3aabc/vmlinux-6fea5fab.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c8feb6df0b6a/bzImage-6fea5fab.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d066dd...@syzkaller.appspotmail.com
loop0: detected capacity change from 0 to 32768
=======================================================
WARNING: The mand mount option has been deprecated and
and is ignored by this kernel. Remove the mand
option from the mount to silence this warning.
=======================================================
ocfs2: Mounting device (7,0) on (node local, slot 0) with ordered data mode.
(syz.0.0,5329,0):ocfs2_extend_trans:438 ERROR: status = -30
(syz.0.0,5329,0):ocfs2_truncate_rec:5445 ERROR: status = -30
(syz.0.0,5329,0):ocfs2_remove_extent:5592 ERROR: status = -30
(syz.0.0,5329,0):__ocfs2_remove_xattr_range:782 ERROR: status = -30
(syz.0.0,5329,0):ocfs2_xattr_shrink_size:836 ERROR: status = -30
(syz.0.0,5329,0):__ocfs2_journal_access:705 ERROR: Error -30 getting 1 access to buffer!
(syz.0.0,5329,0):ocfs2_xa_prepare_entry:2151 ERROR: status = -30
(syz.0.0,5329,0):ocfs2_xa_set:2254 ERROR: status = -30
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN NOPTI
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
CPU: 0 UID: 0 PID: 5329 Comm: syz.0.0 Not tainted 6.15.0-rc2-syzkaller-00488-g6fea5fabd332 #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:jbd2_journal_dirty_metadata+0x1ec/0xc00 fs/jbd2/transaction.c:1531
Code: 8b 5c 24 08 74 08 48 89 df e8 30 a6 93 ff 4c 39 33 0f 84 28 01 00 00 e8 42 6c 29 ff 31 db e9 f8 04 00 00 4c 89 f0 48 c1 e8 03 <42> 80 3c 20 00 74 08 4c 89 f7 e8 05 a6 93 ff 4c 89 74 24 28 49 8b
RSP: 0018:ffffc9000d43e918 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000100000
RDX: ffff888000daa440 RSI: 0000000000000000 RDI: 0000000000000001
RBP: 1ffff11008a0adae R08: ffffffff829950b2 R09: 1ffff11008a34d96
R10: dffffc0000000000 R11: ffffed1008a34d97 R12: dffffc0000000000
R13: 1ffff11008a48a8f R14: 0000000000000000 R15: ffff888045056d20
FS: 00007f894e7a96c0(0000) GS:ffff88808c59a000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00002000000aa000 CR3: 000000004317e000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ocfs2_journal_dirty+0x165/0x7e0 fs/ocfs2/journal.c:812
ocfs2_xa_journal_dirty fs/ocfs2/xattr.c:1453 [inline]
ocfs2_xa_set+0x217c/0x2a40 fs/ocfs2/xattr.c:2263
ocfs2_xattr_block_set+0x46e/0x3360 fs/ocfs2/xattr.c:2985
__ocfs2_xattr_set_handle+0x6e7/0x1100 fs/ocfs2/xattr.c:3387
ocfs2_xattr_set+0x1290/0x1940 fs/ocfs2/xattr.c:3650
__vfs_setxattr+0x468/0x4a0 fs/xattr.c:200
__vfs_setxattr_noperm+0x12e/0x660 fs/xattr.c:234
vfs_setxattr+0x223/0x430 fs/xattr.c:321
do_setxattr fs/xattr.c:636 [inline]
filename_setxattr+0x2dd/0x480 fs/xattr.c:665
path_setxattrat+0x3f7/0x4c0 fs/xattr.c:713
__do_sys_setxattr fs/xattr.c:747 [inline]
__se_sys_setxattr fs/xattr.c:743 [inline]
__x64_sys_setxattr+0xbc/0xe0 fs/xattr.c:743
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xf3/0x210 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f894d98e169
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f894e7a9038 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007f894dbb5fa0 RCX: 00007f894d98e169
RDX: 0000000000000000 RSI: 0000200000000140 RDI: 0000200000000080
RBP: 00007f894da10a68 R08: 0000000000000002 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f894dbb5fa0 R15: 00007ffc388c8c68
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:jbd2_journal_dirty_metadata+0x1ec/0xc00 fs/jbd2/transaction.c:1531
Code: 8b 5c 24 08 74 08 48 89 df e8 30 a6 93 ff 4c 39 33 0f 84 28 01 00 00 e8 42 6c 29 ff 31 db e9 f8 04 00 00 4c 89 f0 48 c1 e8 03 <42> 80 3c 20 00 74 08 4c 89 f7 e8 05 a6 93 ff 4c 89 74 24 28 49 8b
RSP: 0018:ffffc9000d43e918 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000100000
RDX: ffff888000daa440 RSI: 0000000000000000 RDI: 0000000000000001
RBP: 1ffff11008a0adae R08: ffffffff829950b2 R09: 1ffff11008a34d96
R10: dffffc0000000000 R11: ffffed1008a34d97 R12: dffffc0000000000
R13: 1ffff11008a48a8f R14: 0000000000000000 R15: ffff888045056d20
FS: 00007f894e7a96c0(0000) GS:ffff88808c59a000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00002000000aa000 CR3: 000000004317e000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 8b 5c 24 08 mov 0x8(%rsp),%ebx
4: 74 08 je 0xe
6: 48 89 df mov %rbx,%rdi
9: e8 30 a6 93 ff call 0xff93a63e
e: 4c 39 33 cmp %r14,(%rbx)
11: 0f 84 28 01 00 00 je 0x13f
17: e8 42 6c 29 ff call 0xff296c5e
1c: 31 db xor %ebx,%ebx
1e: e9 f8 04 00 00 jmp 0x51b
23: 4c 89 f0 mov %r14,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 20 00 cmpb $0x0,(%rax,%r12,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 4c 89 f7 mov %r14,%rdi
34: e8 05 a6 93 ff call 0xff93a63e
39: 4c 89 74 24 28 mov %r14,0x28(%rsp)
3e: 49 rex.WB
3f: 8b .byte 0x8b
---
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: 6fea5fabd332 Merge tag 'mm-hotfixes-stable-2025-04-19-21-2..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=150feccc580000
kernel config: https://syzkaller.appspot.com/x/.config?x=68d9f79fc685cd4
dashboard link: https://syzkaller.appspot.com/bug?extid=d066dd4ecc8199610806
compiler: Debian clang version 15.0.6, Debian LLD 15.0.6
CC: [ja...@suse.com linux...@vger.kernel.org linux-...@vger.kernel.org ty...@mit.edu]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-6fea5fab.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/196af7f3aabc/vmlinux-6fea5fab.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c8feb6df0b6a/bzImage-6fea5fab.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d066dd...@syzkaller.appspotmail.com
loop0: detected capacity change from 0 to 32768
=======================================================
WARNING: The mand mount option has been deprecated and
and is ignored by this kernel. Remove the mand
option from the mount to silence this warning.
=======================================================
ocfs2: Mounting device (7,0) on (node local, slot 0) with ordered data mode.
(syz.0.0,5329,0):ocfs2_extend_trans:438 ERROR: status = -30
(syz.0.0,5329,0):ocfs2_truncate_rec:5445 ERROR: status = -30
(syz.0.0,5329,0):ocfs2_remove_extent:5592 ERROR: status = -30
(syz.0.0,5329,0):__ocfs2_remove_xattr_range:782 ERROR: status = -30
(syz.0.0,5329,0):ocfs2_xattr_shrink_size:836 ERROR: status = -30
(syz.0.0,5329,0):__ocfs2_journal_access:705 ERROR: Error -30 getting 1 access to buffer!
(syz.0.0,5329,0):ocfs2_xa_prepare_entry:2151 ERROR: status = -30
(syz.0.0,5329,0):ocfs2_xa_set:2254 ERROR: status = -30
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN NOPTI
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
CPU: 0 UID: 0 PID: 5329 Comm: syz.0.0 Not tainted 6.15.0-rc2-syzkaller-00488-g6fea5fabd332 #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:jbd2_journal_dirty_metadata+0x1ec/0xc00 fs/jbd2/transaction.c:1531
Code: 8b 5c 24 08 74 08 48 89 df e8 30 a6 93 ff 4c 39 33 0f 84 28 01 00 00 e8 42 6c 29 ff 31 db e9 f8 04 00 00 4c 89 f0 48 c1 e8 03 <42> 80 3c 20 00 74 08 4c 89 f7 e8 05 a6 93 ff 4c 89 74 24 28 49 8b
RSP: 0018:ffffc9000d43e918 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000100000
RDX: ffff888000daa440 RSI: 0000000000000000 RDI: 0000000000000001
RBP: 1ffff11008a0adae R08: ffffffff829950b2 R09: 1ffff11008a34d96
R10: dffffc0000000000 R11: ffffed1008a34d97 R12: dffffc0000000000
R13: 1ffff11008a48a8f R14: 0000000000000000 R15: ffff888045056d20
FS: 00007f894e7a96c0(0000) GS:ffff88808c59a000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00002000000aa000 CR3: 000000004317e000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ocfs2_journal_dirty+0x165/0x7e0 fs/ocfs2/journal.c:812
ocfs2_xa_journal_dirty fs/ocfs2/xattr.c:1453 [inline]
ocfs2_xa_set+0x217c/0x2a40 fs/ocfs2/xattr.c:2263
ocfs2_xattr_block_set+0x46e/0x3360 fs/ocfs2/xattr.c:2985
__ocfs2_xattr_set_handle+0x6e7/0x1100 fs/ocfs2/xattr.c:3387
ocfs2_xattr_set+0x1290/0x1940 fs/ocfs2/xattr.c:3650
__vfs_setxattr+0x468/0x4a0 fs/xattr.c:200
__vfs_setxattr_noperm+0x12e/0x660 fs/xattr.c:234
vfs_setxattr+0x223/0x430 fs/xattr.c:321
do_setxattr fs/xattr.c:636 [inline]
filename_setxattr+0x2dd/0x480 fs/xattr.c:665
path_setxattrat+0x3f7/0x4c0 fs/xattr.c:713
__do_sys_setxattr fs/xattr.c:747 [inline]
__se_sys_setxattr fs/xattr.c:743 [inline]
__x64_sys_setxattr+0xbc/0xe0 fs/xattr.c:743
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xf3/0x210 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f894d98e169
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f894e7a9038 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007f894dbb5fa0 RCX: 00007f894d98e169
RDX: 0000000000000000 RSI: 0000200000000140 RDI: 0000200000000080
RBP: 00007f894da10a68 R08: 0000000000000002 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f894dbb5fa0 R15: 00007ffc388c8c68
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:jbd2_journal_dirty_metadata+0x1ec/0xc00 fs/jbd2/transaction.c:1531
Code: 8b 5c 24 08 74 08 48 89 df e8 30 a6 93 ff 4c 39 33 0f 84 28 01 00 00 e8 42 6c 29 ff 31 db e9 f8 04 00 00 4c 89 f0 48 c1 e8 03 <42> 80 3c 20 00 74 08 4c 89 f7 e8 05 a6 93 ff 4c 89 74 24 28 49 8b
RSP: 0018:ffffc9000d43e918 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000100000
RDX: ffff888000daa440 RSI: 0000000000000000 RDI: 0000000000000001
RBP: 1ffff11008a0adae R08: ffffffff829950b2 R09: 1ffff11008a34d96
R10: dffffc0000000000 R11: ffffed1008a34d97 R12: dffffc0000000000
R13: 1ffff11008a48a8f R14: 0000000000000000 R15: ffff888045056d20
FS: 00007f894e7a96c0(0000) GS:ffff88808c59a000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00002000000aa000 CR3: 000000004317e000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 8b 5c 24 08 mov 0x8(%rsp),%ebx
4: 74 08 je 0xe
6: 48 89 df mov %rbx,%rdi
9: e8 30 a6 93 ff call 0xff93a63e
e: 4c 39 33 cmp %r14,(%rbx)
11: 0f 84 28 01 00 00 je 0x13f
17: e8 42 6c 29 ff call 0xff296c5e
1c: 31 db xor %ebx,%ebx
1e: e9 f8 04 00 00 jmp 0x51b
23: 4c 89 f0 mov %r14,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 20 00 cmpb $0x0,(%rax,%r12,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 4c 89 f7 mov %r14,%rdi
34: e8 05 a6 93 ff call 0xff93a63e
39: 4c 89 74 24 28 mov %r14,0x28(%rsp)
3e: 49 rex.WB
3f: 8b .byte 0x8b
---
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
Apr 27, 2025, 4:21:13 AM4/27/25
to syzkaller-upst...@googlegroups.com
Sending this report to the next reporting stage.
Reply all
Reply to author
Forward
0 new messages