From: syzbot <syzbot+3c9f079f8fb1d7d331be@syzkaller.appspotmail.com>
To: hirofumi@mail.parknet.co.jp, jack@suse.com,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: Re: [syzbot] [ext4?] WARNING in __find_get_block (2)
Date: Mon, 16 Dec 2024 18:43:26 -0800 [thread overview]
Message-ID: <6760e54e.050a0220.37aaf.0143.GAE@google.com> (raw)
In-Reply-To: <6741d52e.050a0220.1cc393.0010.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: f44d154d6e3d Merge tag 'soc-fixes-6.13' of git://git.kerne..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=14d627e8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1234f097ee657d8b
dashboard link: https://syzkaller.appspot.com/bug?extid=3c9f079f8fb1d7d331be
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15e302df980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1265b4f8580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a0fb07264d5d/disk-f44d154d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/adf6a39fbd67/vmlinux-f44d154d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d07b6ebb722e/bzImage-f44d154d.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/2fe321e2e902/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3c9f079f8fb1d7d331be@syzkaller.appspotmail.com
------------[ cut here ]------------
VFS: brelse: Trying to free free buffer
WARNING: CPU: 1 PID: 5156 at fs/buffer.c:1229 __brelse fs/buffer.c:1229 [inline]
WARNING: CPU: 1 PID: 5156 at fs/buffer.c:1229 brelse include/linux/buffer_head.h:324 [inline]
WARNING: CPU: 1 PID: 5156 at fs/buffer.c:1229 bh_lru_install fs/buffer.c:1346 [inline]
WARNING: CPU: 1 PID: 5156 at fs/buffer.c:1229 __find_get_block+0x109d/0x1150 fs/buffer.c:1400
Modules linked in:
CPU: 1 UID: 0 PID: 5156 Comm: jbd2/sda1-8 Not tainted 6.13.0-rc3-syzkaller-00017-gf44d154d6e3d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024
RIP: 0010:__brelse fs/buffer.c:1229 [inline]
RIP: 0010:brelse include/linux/buffer_head.h:324 [inline]
RIP: 0010:bh_lru_install fs/buffer.c:1346 [inline]
RIP: 0010:__find_get_block+0x109d/0x1150 fs/buffer.c:1400
Code: c7 3c 9a e8 d5 60 dc ff e9 1b f7 ff ff e8 5b 83 78 ff e9 87 f7 ff ff e8 51 83 78 ff 90 48 c7 c7 20 ee 18 8c e8 74 26 39 ff 90 <0f> 0b 90 90 e9 6b f7 ff ff e8 35 83 78 ff 48 c7 c7 40 c8 a8 8e 4c
RSP: 0018:ffffc9001048f440 EFLAGS: 00010246
RAX: 8c4056f058b05800 RBX: 0000000000000000 RCX: ffff888035151e00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc9001048f570 R08: ffffffff81601962 R09: fffffbfff1cfa210
R10: dffffc0000000000 R11: fffffbfff1cfa210 R12: ffff88807a001828
R13: ffff8880b87398b0 R14: ffff88807f336910 R15: ffff88807f335a58
FS: 0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f1a9566c130 CR3: 000000006602e000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__getblk_slow fs/buffer.c:1127 [inline]
bdev_getblk+0x189/0x670 fs/buffer.c:1431
__getblk include/linux/buffer_head.h:380 [inline]
jbd2_journal_get_descriptor_buffer+0x1c3/0x4e0 fs/jbd2/journal.c:968
journal_submit_commit_record+0x11e/0xa90 fs/jbd2/commit.c:129
jbd2_journal_commit_transaction+0x3c10/0x6560 fs/jbd2/commit.c:877
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>
---
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.
next prev parent reply other threads:[~2024-12-17 2:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 13:14 [syzbot] [udf?] WARNING in __find_get_block (2) syzbot
2024-12-17 2:43 ` syzbot [this message]
2024-12-17 14:35 ` [syzbot] [ext4?] " syzbot
2025-02-16 6:11 ` [syzbot] [ocfs2?] " 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=6760e54e.050a0220.37aaf.0143.GAE@google.com \
--to=syzbot+3c9f079f8fb1d7d331be@syzkaller.appspotmail.com \
--cc=hirofumi@mail.parknet.co.jp \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.