From: syzbot <syzbot+96ee12698391289383dd@syzkaller.appspotmail.com>
To: heming.zhao@suse.com, linux-kernel@vger.kernel.org,
ocfs2-devel@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] [ext4?] WARNING in jbd2_journal_update_sb_log_tail
Date: Tue, 14 Jan 2025 17:26:04 -0800 [thread overview]
Message-ID: <67870eac.050a0220.296bc1.0002.GAE@google.com> (raw)
In-Reply-To: <04a9ad29-51de-4b50-a5bb-56f91817639d@suse.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in jbd2_journal_update_sb_log_tail
------------[ cut here ]------------
WARNING: CPU: 0 PID: 6052 at fs/jbd2/journal.c:1882 jbd2_journal_update_sb_log_tail+0x2ba/0x360 fs/jbd2/journal.c:1882
Modules linked in:
CPU: 0 UID: 0 PID: 6052 Comm: jbd2/loop0-29 Not tainted 6.13.0-rc7-syzkaller-00041-g7f5b6a8ec18e-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:jbd2_journal_update_sb_log_tail+0x2ba/0x360 fs/jbd2/journal.c:1882
Code: 30 ff 41 80 3c 2c 00 74 08 4c 89 ff e8 df 48 94 ff 41 80 27 f7 4c 89 f7 e8 83 10 4a 09 31 ed e9 72 fe ff ff e8 57 6a 30 ff 90 <0f> 0b 90 41 80 3c 2c 00 75 d5 eb db 44 89 f1 80 e1 07 80 c1 03 38
RSP: 0018:ffffc900037577f0 EFLAGS: 00010293
RAX: ffffffff826f07c9 RBX: 0000000000000000 RCX: ffff88801c7c0000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: dffffc0000000000 R08: ffffffff826f0799 R09: fffff520006eaeec
R10: dffffc0000000000 R11: fffff520006eaeec R12: 1ffff110060f7000
R13: ffff88802b13001c R14: ffff8880307b80b0 R15: ffff8880307b8000
FS: 0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555563a325c8 CR3: 0000000031c10000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
jbd2_journal_commit_transaction+0x46a/0x6560 fs/jbd2/commit.c:397
kjournald2+0x41c/0x7b0 fs/jbd2/journal.c:201
kthread+0x2f0/0x390 kernel/kthread.c:389
ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
</TASK>
Tested on:
commit: 7f5b6a8e Merge tag 'pci-v6.13-fixes-3' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=169e07c4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=954e5731cdb4e750
dashboard link: https://syzkaller.appspot.com/bug?extid=96ee12698391289383dd
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=155681f8580000
next parent reply other threads:[~2025-01-15 1:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <04a9ad29-51de-4b50-a5bb-56f91817639d@suse.com>
2025-01-15 1:26 ` syzbot [this message]
[not found] <63e6ff86-5573-40cc-b7f3-0ffcf070ba7c@suse.com>
2025-01-15 5:44 ` [syzbot] [ocfs2?] [ext4?] WARNING in jbd2_journal_update_sb_log_tail syzbot
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=67870eac.050a0220.296bc1.0002.GAE@google.com \
--to=syzbot+96ee12698391289383dd@syzkaller.appspotmail.com \
--cc=heming.zhao@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
/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