From: syzbot <syzbot+4af46ee83100e99bce09@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] kernel BUG in f2fs_write_end_io (2)
Date: Thu, 14 May 2026 18:37:03 -0700 [thread overview]
Message-ID: <6a0678bf.170a0220.9c1d9.07f2.GAE@google.com> (raw)
In-Reply-To: <20260515005957.13243-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
kernel BUG in f2fs_write_end_io
f2fs-dbg: READ end_io: index=3 footer_nid=0 ino=0 uptodate=0 dirty=0 rc=-117
f2fs-dbg: READ end_io: index=3 footer_nid=0 ino=0 uptodate=0 dirty=0 rc=-117
f2fs-dbg: WRITE end_io: index=3 footer_nid=0 ino=0 uptodate=0 dirty=0 rc=-117
------------[ cut here ]------------
kernel BUG at fs/f2fs/data.c:394!
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 1 UID: 0 PID: 42 Comm: kworker/u8:2 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Workqueue: bat_events batadv_bla_periodic_work
RIP: 0010:f2fs_write_end_io+0x1a74/0x1ab0 fs/f2fs/data.c:394
Code: c6 20 3d 9b 8b e8 cc d3 f6 fc 90 0f 0b e8 54 c8 93 fd 4c 89 e7 48 c7 c6 20 3d 9b 8b e8 b5 d3 f6 fc 90 0f 0b e8 3d c8 93 fd 90 <0f> 0b e8 35 c8 93 fd 48 8b 7c 24 08 48 c7 c6 20 3d 9b 8b e8 94 d3
RSP: 0018:ffffc90000b47590 EFLAGS: 00010246
RAX: ffffffff8430e123 RBX: 0000000000001000 RCX: ffff88801f2b0000
RDX: 0000000000000100 RSI: 0000000000000000 RDI: 0000000000000100
RBP: dffffc0000000000 R08: 0000000000000000 R09: 0000000000000100
R10: dffffc0000000000 R11: fffff52000168e61 R12: ffffea0000951140
R13: 0000000000001000 R14: 0000000000000003 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff888126274000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000002b72c000 CR4: 00000000003526f0
Call Trace:
<TASK>
blk_update_request+0x57e/0xe60 block/blk-mq.c:1016
blk_mq_end_request+0x3e/0x70 block/blk-mq.c:1178
blk_complete_reqs block/blk-mq.c:1253 [inline]
blk_done_softirq+0x10a/0x160 block/blk-mq.c:1258
handle_softirqs+0x1de/0x6d0 kernel/softirq.c:622
__do_softirq kernel/softirq.c:656 [inline]
__local_bh_enable_ip+0x170/0x2b0 kernel/softirq.c:302
local_bh_enable include/linux/bottom_half.h:33 [inline]
netif_rx+0xb9/0xf0 net/core/dev.c:5775
batadv_bla_send_claim+0xa12/0xeb0 net/batman-adv/bridge_loop_avoidance.c:447
batadv_bla_send_announce net/batman-adv/bridge_loop_avoidance.c:675 [inline]
batadv_bla_periodic_work+0x629/0xae0 net/batman-adv/bridge_loop_avoidance.c:1490
process_one_work kernel/workqueue.c:3314 [inline]
process_scheduled_works+0xb5d/0x1860 kernel/workqueue.c:3397
worker_thread+0xa53/0xfc0 kernel/workqueue.c:3478
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:f2fs_write_end_io+0x1a74/0x1ab0 fs/f2fs/data.c:394
Code: c6 20 3d 9b 8b e8 cc d3 f6 fc 90 0f 0b e8 54 c8 93 fd 4c 89 e7 48 c7 c6 20 3d 9b 8b e8 b5 d3 f6 fc 90 0f 0b e8 3d c8 93 fd 90 <0f> 0b e8 35 c8 93 fd 48 8b 7c 24 08 48 c7 c6 20 3d 9b 8b e8 94 d3
RSP: 0018:ffffc90000b47590 EFLAGS: 00010246
RAX: ffffffff8430e123 RBX: 0000000000001000 RCX: ffff88801f2b0000
RDX: 0000000000000100 RSI: 0000000000000000 RDI: 0000000000000100
RBP: dffffc0000000000 R08: 0000000000000000 R09: 0000000000000100
R10: dffffc0000000000 R11: fffff52000168e61 R12: ffffea0000951140
R13: 0000000000001000 R14: 0000000000000003 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff888126274000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000002b72c000 CR4: 00000000003526f0
Tested on:
commit: 66182ca8 Merge tag 'net-7.1-rc4' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=142d20ec580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f2e8ebfec4636d32
dashboard link: https://syzkaller.appspot.com/bug?extid=4af46ee83100e99bce09
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=1400d636580000
next parent reply other threads:[~2026-05-15 1:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260515005957.13243-1-kartikey406@gmail.com>
2026-05-15 1:37 ` syzbot [this message]
[not found] <20260515015523.14962-1-kartikey406@gmail.com>
2026-05-15 2:37 ` [syzbot] [f2fs?] kernel BUG in f2fs_write_end_io (2) syzbot
[not found] <20260514233543.9626-1-kartikey406@gmail.com>
2026-05-15 0:07 ` syzbot
2026-05-14 20:19 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=6a0678bf.170a0220.9c1d9.07f2.GAE@google.com \
--to=syzbot+4af46ee83100e99bce09@syzkaller.appspotmail.com \
--cc=kartikey406@gmail.com \
--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.