From nobody Sat Feb 7 22:06:30 2026 Received: from mail-oa1-f72.google.com (mail-oa1-f72.google.com [209.85.160.72]) (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 4BDA723ABAA for ; Tue, 3 Feb 2026 05:17:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.160.72 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770095842; cv=none; b=ck8Vg7k7Yi+mI0UevTeCPNDsb3nESsMZw06BIizIhidV/H1LRiHNWtXzCoQvDjKJrpIvX3QVJgRDP3Qm6PYq6zPWGqR0A2ZcdoEqeVKI4kvM1buh03Z2rW5zerlp9IpIySMIR/7N4rVMnSjeS/HfYyA+52uN+Jlz6J+2qHayT0U= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770095842; c=relaxed/simple; bh=qJC148TVxtK+ycZN0ztFAQKjHFxvbtYn1GW2ry/AkuE=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To: Content-Type; b=oJ6AQhRqjNmdUCDnPjnsY+Hzh1vDQGjqtXuhLU4ZVRIvdrPK0oY6dT4rStnnJ21nt6va5HPPkgHi+jEL51EX0VKVvo7qYD9CUO6MJ8eickItjdLulZIF3BitRzX4v61AUlpxa23ZR2IHQkcQ5MImAd6n4QeSOHdKnVtW0C+joUU= 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.160.72 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-oa1-f72.google.com with SMTP id 586e51a60fabf-4097bb790e5so2063793fac.1 for ; Mon, 02 Feb 2026 21:17:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1770095840; x=1770700640; 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=FrlvELVXU1jXncI1P9GuifflpK5gCgIUksjvwP/GI+U=; b=TJ4mp5h00jT/FmzrlFLdl7j2pMDF3ky7vbYX+2oJlGxlVN5UT64YvtZwG6Vncs7Jnc ypCfw5TEjXdDiAM+XbxTOIfAX03Vs6817kRX/IQ6l9eafZUND5R47PqtBCqQ1FO8+FTV mDdAkmloy4d8fAteUv8eMo4Gw4QeZHQ4ZO1xyWVv9vWtq2oDGXIBs2T2PnHxGO/Y8P3Q 25ZognABoyACGBigNlzrN828EwTcCNQ910OpSMYCOhOx85eQ/8+VVxL6NeyqdD5DQqcs d+twdUFJjZN+X3s8UE4BsCi5PEMqjT9iSNhlO0KrvQOIhHVLJV9JBkQjxlnYJPJ5EW8U 2M+Q== X-Gm-Message-State: AOJu0YyGMP9OLQYjesPC9r9DBQ1Xu8EyHPQ4MyNPMT9TMHaHV4A1qBa3 rJPlPW6ot2riCgeTl1vuKYA4DXJf8ARDNMe4sIgyCfsMpjJYQlfAFkveF/bWJMklkLcFzMtYl9s T8v4orXSfdXEgOl05aYy3/cMud5h2VR86gPp4SUaDW0aUBx6vkKLtI17CW7s= 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:985:b0:662:fb1b:ff9d with SMTP id 006d021491bc7-668c82932b0mr903627eaf.19.1770095840195; Mon, 02 Feb 2026 21:17:20 -0800 (PST) Date: Mon, 02 Feb 2026 21:17:20 -0800 In-Reply-To: <6980e9ff.050a0220.16b13.00a9.GAE@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <698184e0.050a0220.3b3015.0003.GAE@google.com> Subject: Forwarded: [PATCH] ext4: add debug logging for inline data flag in ext4_iget From: syzbot To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" For archival purposes, forwarding an incoming command email to linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com. *** Subject: [PATCH] ext4: add debug logging for inline data flag in ext4_iget Author: kartikey406@gmail.com #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git= master Add debug printk statements to track inline data flag status and inode size during inode loading. This helps diagnose corruption issues where the EXT4_INLINE_DATA_FL flag may be set inconsistently with the actual inode size. The debug output logs: - Raw inode mode, flags, and size fields - Whether INLINE_DATA flag is set - Whether EXTENTS flag is set This is useful for investigating crashes in ext4_write_inline_data() where the BUG_ON(pos + len > EXT4_I(inode)->i_inline_size) triggers due to corrupted filesystem images that have inline data flag set but file size exceeding inline capacity. Reported-by: syzbot+7de5fe447862fc37576f@syzkaller.appspotmail.com Link: https://syzkaller.appspot.com/bug?extid=3D7de5fe447862fc37576f Signed-off-by: Deepanshu Kartikey --- fs/ext4/inode.c | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c index 0c466ccbed69..ad6eff690edd 100644 --- a/fs/ext4/inode.c +++ b/fs/ext4/inode.c @@ -5211,6 +5211,22 @@ struct inode *__ext4_iget(struct super_block *sb, un= signed long ino, goto bad_inode; raw_inode =3D ext4_raw_inode(&iloc); =20 + printk(KERN_WARNING "EXT4-fs DEBUG: inode=3D%lu i_mode=3D0x%x i_flags=3D0= x%x i_size_lo=3D%u i_size_hi=3D%u\n", + ino, + le16_to_cpu(raw_inode->i_mode), + le32_to_cpu(raw_inode->i_flags), + le32_to_cpu(raw_inode->i_size_lo), + le32_to_cpu(raw_inode->i_size_high)); + /* Check if inline flag is set in raw flags */ + if (le32_to_cpu(raw_inode->i_flags) & EXT4_INLINE_DATA_FL) { + printk(KERN_WARNING "EXT4-fs DEBUG: inode=3D%lu has INLINE_DATA flag set= !\n", ino); + } + + /* Check if extents flag is set in raw flags */ + if (le32_to_cpu(raw_inode->i_flags) & EXT4_EXTENTS_FL) { + printk(KERN_WARNING "EXT4-fs DEBUG: inode=3D%lu has EXTENTS flag set!\n"= , ino); + } + if ((flags & EXT4_IGET_HANDLE) && (raw_inode->i_links_count =3D=3D 0) && (raw_inode->i_mode =3D=3D 0)) { ret =3D -ESTALE; --=20 2.43.0