From: syzbot <syzbot+9bbc6788187abbabb2ee@syzkaller.appspotmail.com>
To: dwmw2@infradead.org, linux-kernel@vger.kernel.org,
linux-mtd@lists.infradead.org, richard@nod.at,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [jffs2?] kernel BUG in jffs2_garbage_collect_pass
Date: Sun, 09 Aug 2026 17:25:31 -0700 [thread overview]
Message-ID: <6a791a7b.01d0871a.3a0d52.0098.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 562bfb501c54 Merge tag 'integrity-v7.2-rc7' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13a35bb9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=cb17729fb04b1e3a
dashboard link: https://syzkaller.appspot.com/bug?extid=9bbc6788187abbabb2ee
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/dc0b8603d3a0/disk-562bfb50.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/08c750d8b185/vmlinux-562bfb50.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6142deb5b95c/bzImage-562bfb50.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9bbc6788187abbabb2ee@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/jffs2/gc.c:226!
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 7620 Comm: jffs2_gcd_mtd0 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:jffs2_garbage_collect_pass+0x20e7/0x2170 fs/jffs2/gc.c:226
Code: 6b f7 fd 48 8b 7c 24 20 e8 06 6b 16 08 90 0f 0b e8 de de 95 fe bf 02 00 00 00 e8 34 44 64 fe e9 9d e7 ff ff e8 ca de 95 fe 90 <0f> 0b e8 c2 de 95 fe bf 02 00 00 00 e8 18 44 64 fe e9 7a f8 ff ff
RSP: 0018:ffffc900041b7aa0 EFLAGS: 00010293
RAX: ffffffff832ffa76 RBX: 0000000000000006 RCX: ffff888029738000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc900041b7c70 R08: ffff888029738000 R09: 0000000000000006
R10: 0000000000000100 R11: 0000000000000005 R12: ffff8880357c6410
R13: ffff88805f5ef700 R14: 1ffff1100bebdee2 R15: ffff88805f5ef712
FS: 0000000000000000(0000) GS:ffff888125c3e000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f06a384fffc CR3: 0000000056094000 CR4: 00000000003526f0
Call Trace:
<TASK>
jffs2_garbage_collect_thread+0x634/0x6c0 fs/jffs2/background.c:155
kthread+0x388/0x470 kernel/kthread.c:436
ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:jffs2_garbage_collect_pass+0x20e7/0x2170 fs/jffs2/gc.c:226
Code: 6b f7 fd 48 8b 7c 24 20 e8 06 6b 16 08 90 0f 0b e8 de de 95 fe bf 02 00 00 00 e8 34 44 64 fe e9 9d e7 ff ff e8 ca de 95 fe 90 <0f> 0b e8 c2 de 95 fe bf 02 00 00 00 e8 18 44 64 fe e9 7a f8 ff ff
RSP: 0018:ffffc900041b7aa0 EFLAGS: 00010293
RAX: ffffffff832ffa76 RBX: 0000000000000006 RCX: ffff888029738000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc900041b7c70 R08: ffff888029738000 R09: 0000000000000006
R10: 0000000000000100 R11: 0000000000000005 R12: ffff8880357c6410
R13: ffff88805f5ef700 R14: 1ffff1100bebdee2 R15: ffff88805f5ef712
FS: 0000000000000000(0000) GS:ffff888125c3e000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f06a384fffc CR3: 0000000056094000 CR4: 00000000003526f0
---
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-08-10 0:25 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=6a791a7b.01d0871a.3a0d52.0098.GAE@google.com \
--to=syzbot+9bbc6788187abbabb2ee@syzkaller.appspotmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--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