public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+a5f824f1c49dd97fcff0@syzkaller.appspotmail.com>
To: jack@suse.com, linux-ext4@vger.kernel.org,
	linux-kernel@vger.kernel.org,  syzkaller-bugs@googlegroups.com,
	tytso@mit.edu
Subject: [syzbot] [ext4?] WARNING in jbd2_journal_dirty_metadata (3)
Date: Wed, 22 Apr 2026 15:44:26 -0700	[thread overview]
Message-ID: <69e94f4a.a00a0220.9259.0022.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    eb5249b12507 Merge tag 'parisc-for-7.1-rc1' of git://git.k..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16ed0836580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d120b114be21f79
dashboard link: https://syzkaller.appspot.com/bug?extid=a5f824f1c49dd97fcff0
compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-eb5249b1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cb4e868ca1f9/vmlinux-eb5249b1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fb064cd651ff/bzImage-eb5249b1.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a5f824f1c49dd97fcff0@syzkaller.appspotmail.com

loop0: detected capacity change from 0 to 32768
JBD2: Ignoring recovery information on journal
ocfs2: Mounting device (7,0) on (node local, slot 0) with ordered data mode.
------------[ cut here ]------------
jbd2_handle_buffer_credits(handle) <= 0
WARNING: fs/jbd2/transaction.c:1593 at jbd2_journal_dirty_metadata+0x9c8/0xd30 fs/jbd2/transaction.c:1593, CPU#0: syz.0.0/5322
Modules linked in:
CPU: 0 UID: 0 PID: 5322 Comm: syz.0.0 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:jbd2_journal_dirty_metadata+0x9c8/0xd30 fs/jbd2/transaction.c:1593
Code: 26 03 00 00 45 8b 06 48 c7 c7 40 07 e6 8b 89 de 89 ea 4c 89 f9 e8 18 25 8a fe b8 ea ff ff ff e9 11 fa ff ff e8 f9 42 28 ff 90 <0f> 0b 90 b8 e4 ff ff ff e9 fe f9 ff ff e8 e6 42 28 ff 90 0f 0b 90
RSP: 0018:ffffc9000f85e640 EFLAGS: 00010287
RAX: ffffffff829d9bb7 RBX: 0000000000000000 RCX: 0000000000100000
RDX: ffffc9000ef42000 RSI: 000000000009fb83 RDI: 000000000009fb84
RBP: 1ffff1100ac32d99 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff52001f0bcb8 R12: ffff8880483456f8
R13: ffff888048345690 R14: 1ffff11009068adc R15: 0000000000000000
FS:  00007f04675f56c0(0000) GS:ffff88808c81a000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055a18f887168 CR3: 000000001f4fd000 CR4: 0000000000352ef0
Call Trace:
 <TASK>
 ocfs2_journal_dirty+0x130/0x700 fs/ocfs2/journal.c:831
 ocfs2_alloc_dinode_update_counts+0x16e/0x2d0 fs/ocfs2/suballoc.c:1746
 ocfs2_search_chain+0xe39/0x1e10 fs/ocfs2/suballoc.c:2002
 ocfs2_claim_suballoc_bits+0x901/0x1f40 fs/ocfs2/suballoc.c:2113
 __ocfs2_claim_clusters+0x31d/0x970 fs/ocfs2/suballoc.c:2540
 ocfs2_make_clusters_writable fs/ocfs2/refcounttree.c:3243 [inline]
 ocfs2_replace_cow+0x984/0x1c90 fs/ocfs2/refcounttree.c:3346
 ocfs2_refcount_cow_hunk fs/ocfs2/refcounttree.c:3424 [inline]
 ocfs2_refcount_cow+0x790/0xd40 fs/ocfs2/refcounttree.c:3467
 ocfs2_prepare_inode_for_write fs/ocfs2/file.c:2347 [inline]
 ocfs2_file_write_iter+0xee2/0x1e70 fs/ocfs2/file.c:2458
 iter_file_splice_write+0x9a1/0x10f0 fs/splice.c:736
 do_splice_from fs/splice.c:936 [inline]
 direct_splice_actor+0x101/0x160 fs/splice.c:1159
 splice_direct_to_actor+0x53a/0xc70 fs/splice.c:1103
 do_splice_direct_actor fs/splice.c:1202 [inline]
 do_splice_direct+0x195/0x290 fs/splice.c:1228
 do_sendfile+0x535/0x7d0 fs/read_write.c:1372
 __do_sys_sendfile64 fs/read_write.c:1433 [inline]
 __se_sys_sendfile64+0x144/0x1a0 fs/read_write.c:1419
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x15f/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f046b19c819
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f04675f4fe8 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007f046b415fa0 RCX: 00007f046b19c819
RDX: 0000000000000000 RSI: 000000000000000b RDI: 000000000000000a
RBP: 00007f046b232c91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000020fffe82 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f046b416038 R14: 00007f046b415fa0 R15: 00007ffd208882e8
 </TASK>


---
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 syzkaller@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

                 reply	other threads:[~2026-04-22 22:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=69e94f4a.a00a0220.9259.0022.GAE@google.com \
    --to=syzbot+a5f824f1c49dd97fcff0@syzkaller.appspotmail.com \
    --cc=jack@suse.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox