From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oo1-f78.google.com (mail-oo1-f78.google.com [209.85.161.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D951E2853E9 for ; Sun, 17 May 2026 03:07:15 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.161.78 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778987237; cv=none; b=dbZKMfGnC7WQ+je0UnaN/14BvL/YoC87gHuVbqtOPKcg+v5zuuX+htumYBU3oIqoB8YRE8AhAM/k6r6zK5BM5O96iJv10HBH17COW4tGGaCCyZHwOVKWIdaDzr1X+p+4yGuFxdhVXctbuqQ0U2AvnByAN8Oc6S8H0TZMB+XffyY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778987237; c=relaxed/simple; bh=qlUq21C0S2zME+wKVFlmV0jM6QnrPK8PJsWI7D9FnHY=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To: Content-Type; b=qHGKea/DXkMFqYt3FUYo/C1kqynhj33DzfIeHkwIBV2/FOqEWCtUVpPJxKBKyi+RUJM74Vg6AS8VxJNZgJ9iebwRy1O9ytbB1W6cUJsz1FULMQQlIb9gf1R6jdP5IIbR4UM3gCJYDbiluUl3WvrHOr5FeZ5xZ4txyVV0l2NaV5E= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.161.78 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-oo1-f78.google.com with SMTP id 006d021491bc7-6967fe3eeb1so1088410eaf.0 for ; Sat, 16 May 2026 20:07:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1778987235; x=1779592035; h=to:from:subject:message-id:in-reply-to:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=dAZ6z+UA93t59g/j03VJJMlFCV+hVa7MMXfZMlM9Dj4=; b=BoMF7uK2nWK2d7Lsn7bIEMvATBJCi1o3TfVO7O/blSKMyZvGP8/S6tptfGLlA7mGgr pdScazeFtQgbtJadsLlhDqgPfhLY3e48wzAnmIfmsQ1XgcWIuLMGiezs5x3ptoZU7S8R G/u/JEcA7zU9zAAdkoJYy8KpiCh5GblgI8pOupHq4rOCTQPe8zcZXLmefp3HCupg9dFM ZkckubGxmJOQaecoL8pIvJX+pHa4mguUTLCUsa+QUBtZfeCbVvgVuvVYhcOyuFUII/9c CrSfxMQmjRdF8RqSPTfxebmE34hT/5uKd5Hwn98Z2e5X9EbkrUabW01e0GIGco39CRIG YsRQ== X-Gm-Message-State: AOJu0Yxl9MI1Yy4r0Ma+gbBGE3sSLqkiSlWaBwiraL3bn96XQBPah/5H 5jDln6aFttEOamI8HjmEPGlbPoLWu3joJXfb3OynPy8ItzT793/tYsT5qNBNBbF2VN2mzv6uKgy slKBXguzEIlJ2ZsLD6OwuolEU2PXBF+ojo/eMAe2+3gD382SpCBb8LaiBJ3oGFw== Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6820:616:b0:696:2cb1:a007 with SMTP id 006d021491bc7-69c9435cea1mr6469973eaf.24.1778987234861; Sat, 16 May 2026 20:07:14 -0700 (PDT) Date: Sat, 16 May 2026 20:07:14 -0700 In-Reply-To: <6a062e5c.170a0220.196691.0007.GAE@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6a0930e2.050a0220.f80e4.0007.GAE@google.com> Subject: Forwarded: Re: [syzbot] [f2fs?] kernel BUG in f2fs_write_end_io (2) From: syzbot To: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" For archival purposes, forwarding an incoming command email to linux-kernel@vger.kernel.org. *** Subject: Re: [syzbot] [f2fs?] kernel BUG in f2fs_write_end_io (2) Author: chao@kernel.org #syz test: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git bugfix/syzbot On 5/14/26 20:19, syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit: aa54b1d27fe0 rxrpc: Also unshare DATA/RESPONSE packets whe.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=14adabce580000 > 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 > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1643c3ce580000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12adabce580000 > > Downloadable assets: > disk image: https://storage.googleapis.com/syzbot-assets/418e3ed628cf/disk-aa54b1d2.raw.xz > vmlinux: https://storage.googleapis.com/syzbot-assets/a35b53d0ab2f/vmlinux-aa54b1d2.xz > kernel image: https://storage.googleapis.com/syzbot-assets/03c3fa0081b4/bzImage-aa54b1d2.xz > mounted in repro #1: https://storage.googleapis.com/syzbot-assets/13e397c7f935/mount_0.gz > fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=158fad06580000) > mounted in repro #2: https://storage.googleapis.com/syzbot-assets/2f91edde40dc/mount_8.gz > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > Reported-by: syzbot+4af46ee83100e99bce09@syzkaller.appspotmail.com > > ------------[ cut here ]------------ > kernel BUG at fs/f2fs/data.c:388! > Oops: invalid opcode: 0000 [#1] SMP KASAN PTI > CPU: 1 UID: 0 PID: 31 Comm: ksoftirqd/1 Not tainted syzkaller #0 PREEMPT_{RT,(full)} > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026 > RIP: 0010:f2fs_write_end_io+0x16df/0x1740 fs/f2fs/data.c:388 > Code: 20 3c 9b 8b e8 12 0a f7 fc 90 0f 0b e8 0a cc 93 fd 48 8b 3c 24 48 c7 c6 20 3c 9b 8b e8 fa 09 f7 fc 90 0f 0b e8 f2 cb 93 fd 90 <0f> 0b e8 ea cb 93 fd 48 8b 3c 24 48 c7 c6 20 3c 9b 8b e8 da 09 f7 > RSP: 0018:ffffc90000a5fb18 EFLAGS: 00010246 > RAX: ffffffff8430aade RBX: ffffea0000d91c40 RCX: ffff88801d6b0000 > RDX: 0000000000000100 RSI: 0000000000000000 RDI: 0000000000000100 > RBP: dffffc0000000000 R08: 0000000000000000 R09: 0000000000000100 > R10: dffffc0000000000 R11: fffffbfff1f11dff R12: 0000000036471000 > R13: ffffea0000d91c80 R14: 000000000000000b R15: 0000000000000000 > FS: 0000000000000000(0000) GS:ffff888126276000(0000) knlGS:0000000000000000 > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: 00007eff6352cff8 CR3: 000000002caa2000 CR4: 00000000003526f0 > Call Trace: > > 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 > run_ksoftirqd+0x52/0x180 kernel/softirq.c:1076 > smpboot_thread_fn+0x541/0xa50 kernel/smpboot.c:160 > 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 > > Modules linked in: > ---[ end trace 0000000000000000 ]--- > RIP: 0010:f2fs_write_end_io+0x16df/0x1740 fs/f2fs/data.c:388 > Code: 20 3c 9b 8b e8 12 0a f7 fc 90 0f 0b e8 0a cc 93 fd 48 8b 3c 24 48 c7 c6 20 3c 9b 8b e8 fa 09 f7 fc 90 0f 0b e8 f2 cb 93 fd 90 <0f> 0b e8 ea cb 93 fd 48 8b 3c 24 48 c7 c6 20 3c 9b 8b e8 da 09 f7 > RSP: 0018:ffffc90000a5fb18 EFLAGS: 00010246 > RAX: ffffffff8430aade RBX: ffffea0000d91c40 RCX: ffff88801d6b0000 > RDX: 0000000000000100 RSI: 0000000000000000 RDI: 0000000000000100 > RBP: dffffc0000000000 R08: 0000000000000000 R09: 0000000000000100 > R10: dffffc0000000000 R11: fffffbfff1f11dff R12: 0000000036471000 > R13: ffffea0000d91c80 R14: 000000000000000b R15: 0000000000000000 > FS: 0000000000000000(0000) GS:ffff888126276000(0000) knlGS:0000000000000000 > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: 00007eff6352cff8 CR3: 000000002caa2000 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 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. > > 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