From: syzbot <syzbot+53bb24d476ef8368a7f0@syzkaller.appspotmail.com>
To: kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] kernel BUG in __journal_res_get (2)
Date: Mon, 16 Dec 2024 00:10:20 -0800 [thread overview]
Message-ID: <675fe06c.050a0220.37aaf.011c.GAE@google.com> (raw)
In-Reply-To: <6735aa91.050a0220.2a2fcc.0062.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 2e7aff49b5da Merge branches 'for-next/core' and 'for-next/..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=1129a60f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=696fb014d05da3a3
dashboard link: https://syzkaller.appspot.com/bug?extid=53bb24d476ef8368a7f0
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=12b547e8580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10baf344580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ef408f67fde3/disk-2e7aff49.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/414ac17a20dc/vmlinux-2e7aff49.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a93415d2a7e7/Image-2e7aff49.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/6280c05687f7/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+53bb24d476ef8368a7f0@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/bcachefs/journal.c:359!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 UID: 0 PID: 6423 Comm: syz-executor145 Not tainted 6.13.0-rc2-syzkaller-g2e7aff49b5da #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : journal_entry_open fs/bcachefs/journal.c:359 [inline]
pc : __journal_res_get+0x1d80/0x1f60 fs/bcachefs/journal.c:544
lr : journal_entry_open fs/bcachefs/journal.c:359 [inline]
lr : __journal_res_get+0x1d80/0x1f60 fs/bcachefs/journal.c:544
sp : ffff80009e026b00
x29: ffff80009e026d80 x28: 000000000000000a x27: 0000000000effffe
x26: 8111000080100103 x25: ffff0000dcacab40 x24: ffff0000dcacab40
x23: ffff0000dcacab38 x22: dfff800000000000 x21: 1fffe0001b959545
x20: 1fffe0001b9594a0 x19: ffff0000dcaca500 x18: ffff80009e0267e0
x17: 000000000000e53f x16: ffff80008045f36c x15: 0000000000000001
x14: 1fffe0001b959567 x13: 0000000000000000 x12: 0000000000000000
x11: ffff60001b959568 x10: 0000000000ff0100 x9 : 0000000000000000
x8 : ffff0000c6acdac0 x7 : 0000000000000000 x6 : 0000000000000000
x5 : ffff800093532ec8 x4 : 0000000000000008 x3 : ffff800082b728f0
x2 : 0000000000000000 x1 : 0000000000000002 x0 : 0000000000000000
Call trace:
journal_entry_open fs/bcachefs/journal.c:359 [inline] (P)
__journal_res_get+0x1d80/0x1f60 fs/bcachefs/journal.c:544 (P)
journal_entry_open fs/bcachefs/journal.c:359 [inline] (L)
__journal_res_get+0x1d80/0x1f60 fs/bcachefs/journal.c:544 (L)
bch2_journal_res_get_slowpath+0xe0/0x618 fs/bcachefs/journal.c:606
bch2_journal_res_get+0x124/0x1b4 fs/bcachefs/journal.h:382
bch2_journal_meta+0x9c/0x26c fs/bcachefs/journal.c:842
bch2_journal_flush_device_pins+0x3b0/0x5e0 fs/bcachefs/journal_reclaim.c:889
bch2_data_job+0x290/0xa90 fs/bcachefs/move.c:1065
bch2_data_thread+0xc0/0x178 fs/bcachefs/chardev.c:438
kthread+0x288/0x310 kernel/kthread.c:389
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:862
Code: 17ffff9f 976c947b d4210000 976c9479 (d4210000)
---[ end trace 0000000000000000 ]---
---
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-16 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 7:45 [syzbot] [bcachefs?] kernel BUG in __journal_res_get (2) syzbot
2024-12-16 8:10 ` syzbot [this message]
2025-03-10 14:05 ` 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=675fe06c.050a0220.37aaf.011c.GAE@google.com \
--to=syzbot+53bb24d476ef8368a7f0@syzkaller.appspotmail.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.