From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ot1-f78.google.com (mail-ot1-f78.google.com [209.85.210.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 0FD08219301 for ; Wed, 4 Feb 2026 00:52:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.210.78 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770166364; cv=none; b=oW47u/v5CPDD3RwDR3j1rQaCSjQYz1c7nQayg/1/T7KsGZwol5JoZTzCzvRXL/z13Xowi9ofVUaVeinN/6sfJiXyAOAUCGSTfyM5wvmnDfIkx9OGCrXe2bjIxphbaX6B9fSBtpLrrmzau2uf7iox5aeBOIWRVhPXL0SkDbOnDds= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770166364; c=relaxed/simple; bh=XH8Pfcr+i+C2TTkyvB19qdoQE5od25yTBcCgqtC/Les=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=EVQneguGHAyznLmmzpLpBMux3HG/7GHrKLNPiAqzSGBqINco0zpVpQCF703fQLLwcf8GkahvvHTovvnP5GqeJ2c9aWz/Dq1XIPxGcST6pV7WvGZYuGtsTA/PW5j1I/HVnfHm9Vo4OnYIGQy5muXpqttc4yyOWeHUhXnyDS5K9ks= 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.210.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-ot1-f78.google.com with SMTP id 46e09a7af769-7d1872bbb5eso19245447a34.1 for ; Tue, 03 Feb 2026 16:52:42 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1770166362; x=1770771162; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=5l+3JuWEfhBcu/8mKPii3bWEnKBagb3Z3aFKH97yzjs=; b=OFEnHbfHIjvKpJpUCvh5N4T96Rv59Buo9QCdRS+TLKzeFSs7a7/aAB/VqbzGOlqU6O Qq13tf14XQoDFhSfK4i4fMVUM1u/LMj16ONp/ZkIxZCEud2+bZSa9o5hGSPVjd3CVEX9 yL9EUIrxFpwqiRtnbkeWjzULDNrZDtc1mXPEKylFVtoxeV6PRpNLGMtuIHxSsU0o5vUV FFSFanJ4bH9CwSbgXsqocMysZWuxEPb+ugLVXxvNIJVf60k98D2EdrUBCQYQYcKSGorC vv0aliQ2HZQVAo7ukUhcoAbqGpEEM5rnlb1QEjeiXbRuD8B56OHIOGKVD2KOwnhiDwtX fmmA== X-Forwarded-Encrypted: i=1; AJvYcCXS5HSo8p8aRqsN9iXjBhyk9F1V1Jz0ImhQcijDveNV9wsDmjlDHAHIkq53nf6UvR+N9xMegjy4rcjMOBg=@vger.kernel.org X-Gm-Message-State: AOJu0YzJgws5javxydMTBMQuLawkx1vh9J4pHprQNBACGYQreOw/2xF1 IA4SvuHZ7jDYe/VmVOQgcdMbFgtBgHxGmPzn3DaMfQT3Aolk/xlSfb35SlG6KlbHy/lMb+Ho0kT 8Jz6S8aVbTDE+sXilD77FquihoUYF49ntAJqftMblzsos3nJEbQIPlZiEbt8= 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:468d:b0:662:fa5a:b2f1 with SMTP id 006d021491bc7-66a234336e6mr609697eaf.63.1770166362060; Tue, 03 Feb 2026 16:52:42 -0800 (PST) Date: Tue, 03 Feb 2026 16:52:42 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6982985a.a00a0220.37c87e.0017.GAE@google.com> Subject: [syzbot] [f2fs?] kernel BUG in clear_inode (5) From: syzbot To: chao@kernel.org, jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: dee65f79364c Merge tag 'lsm-pr-20260202' of git://git.kern.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1639fbfa580000 kernel config: https://syzkaller.appspot.com/x/.config?x=151a39927f1e10b4 dashboard link: https://syzkaller.appspot.com/bug?extid=fc026e87558558f75c00 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=114fb322580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1245fc5a580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/d5a48068ae28/disk-dee65f79.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/2c254f049b04/vmlinux-dee65f79.xz kernel image: https://storage.googleapis.com/syzbot-assets/12b280dac533/bzImage-dee65f79.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/bce313ec1951/mount_0.gz fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=164fb322580000) IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+fc026e87558558f75c00@syzkaller.appspotmail.com F2FS-fs (loop0): Wrong SSA boundary, start(3584) end(4096) blocks(3072) F2FS-fs (loop0): Can't find valid F2FS filesystem in 1th superblock F2FS-fs (loop0): Image doesn't support compression F2FS-fs (loop0): invalid crc value ------------[ cut here ]------------ kernel BUG at fs/inode.c:782! Oops: invalid opcode: 0000 [#1] SMP KASAN PTI CPU: 1 UID: 0 PID: 6061 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026 RIP: 0010:clear_inode+0x19a/0x1c0 fs/inode.c:782 Code: 4c 89 f7 e8 08 2f eb ff e9 5a ff ff ff 44 89 f1 80 e1 07 80 c1 03 38 c1 7c a2 4c 89 f7 e8 de 2f eb ff eb 98 e8 47 c7 86 ff 90 <0f> 0b e8 3f c7 86 ff 90 0f 0b e8 37 c7 86 ff 90 0f 0b e8 2f c7 86 RSP: 0018:ffffc90003e17850 EFLAGS: 00010293 RAX: ffffffff823c6d29 RBX: ffff888057a99310 RCX: ffff88802b1edac0 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc90003e179c0 R08: 0000000000000000 R09: 0000000000000000 R10: dffffc0000000000 R11: fffffbfff1e8fbef R12: dffffc0000000000 R13: 1ffff920007c2f1c R14: ffff888057a99568 R15: 0000000000000001 FS: 000055557a53e500(0000) GS:ffff8881266c9000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fff6ffc5bbc CR3: 0000000034a72000 CR4: 00000000003526f0 Call Trace: evict+0x61e/0xb10 fs/inode.c:837 f2fs_fill_super+0x54e4/0x6e30 fs/f2fs/super.c:5147 get_tree_bdev_flags+0x431/0x4f0 fs/super.c:1691 vfs_get_tree+0x92/0x2a0 fs/super.c:1751 fc_mount fs/namespace.c:1199 [inline] do_new_mount_fc fs/namespace.c:3636 [inline] do_new_mount+0x329/0xa50 fs/namespace.c:3712 do_mount fs/namespace.c:4035 [inline] __do_sys_mount fs/namespace.c:4224 [inline] __se_sys_mount+0x31d/0x420 fs/namespace.c:4201 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xe2/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7ff95c0cc14a Code: 48 c7 c2 e8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffd4f028d88 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 00007ffd4f028e10 RCX: 00007ff95c0cc14a RDX: 0000200000000140 RSI: 00002000000001c0 RDI: 00007ffd4f028dd0 RBP: 0000200000000140 R08: 00007ffd4f028e10 R09: 0000000000000008 R10: 0000000000000008 R11: 0000000000000246 R12: 00002000000001c0 R13: 00007ffd4f028dd0 R14: 0000000000005548 R15: 0000200000000200 Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:clear_inode+0x19a/0x1c0 fs/inode.c:782 Code: 4c 89 f7 e8 08 2f eb ff e9 5a ff ff ff 44 89 f1 80 e1 07 80 c1 03 38 c1 7c a2 4c 89 f7 e8 de 2f eb ff eb 98 e8 47 c7 86 ff 90 <0f> 0b e8 3f c7 86 ff 90 0f 0b e8 37 c7 86 ff 90 0f 0b e8 2f c7 86 RSP: 0018:ffffc90003e17850 EFLAGS: 00010293 RAX: ffffffff823c6d29 RBX: ffff888057a99310 RCX: ffff88802b1edac0 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc90003e179c0 R08: 0000000000000000 R09: 0000000000000000 R10: dffffc0000000000 R11: fffffbfff1e8fbef R12: dffffc0000000000 R13: 1ffff920007c2f1c R14: ffff888057a99568 R15: 0000000000000001 FS: 000055557a53e500(0000) GS:ffff8881266c9000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fff6ffc5bbc CR3: 0000000034a72000 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