From nobody Tue Apr 7 10:57:23 2026 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 049403E0229; Fri, 13 Mar 2026 18:45:33 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773427533; cv=none; b=amibnnThqcWBu762wOpHBGh7RiW8qPZJzrCQ/iZT5kO1CDwSo1Uh6JXMyVPvcxPIVRTnUMLDyjtEZZjNCIew/9Zn4jsrJ9lZxhr6TYOiRcAOJGSrQXZHm6YxtRbHmkohp0kM/MaXrfy464RWQkpi9kOgGVBKIHMtgGP6Y2bSwyY= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773427533; c=relaxed/simple; bh=Vytham6oPFTdVP7zlc8wsX2dbeVuNOdhbpe3qUY80eE=; h=From:Date:Subject:MIME-Version:Content-Type:Message-Id:References: In-Reply-To:To:Cc; b=bsAwdcjx5WHAo/3oBxc5Omx0+dCJqeYjdgyI9pbaE/7h6UDGQ/6m5PcPEfHcPbWPZ79G3kDZFTg363W+iJ/X9YEF6t+S21uNKdIxTCkeHKT7/3+FdCLEWJU1QPaQWUX3pV+Y2/a0xxJKSpURKvGFc76roiQV5Uu8SYe1lP1TBe4= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=PYtz5RvO; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="PYtz5RvO" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7F053C19421; Fri, 13 Mar 2026 18:45:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1773427532; bh=Vytham6oPFTdVP7zlc8wsX2dbeVuNOdhbpe3qUY80eE=; h=From:Date:Subject:References:In-Reply-To:To:Cc:From; b=PYtz5RvOFHnpksyifzWqrlcNXD2mHixGwo2ZnIHp+6xKrAc1RCwElMZT56yO5H2Tn 6Yh05DQWwXyZ0nkoqVReUaEADDYXaRpXKZyxeNw4KylJY/jZdTQjXKIpMam5bPZCVp +xMiXFpsOghYgE5iOYSx5JcQfBCno9D/HVWpRM0pgZZAK86po9ontPVMFif2N4jV5L T4V07FVs7Sr76drRFa0OE5d48E2mJR8PvhrAoiWkRJy6wpSTroAQ2r9GXMg03Tq1Ir OXSYyoxpU+qeBj0thU8pXO93XzgdLUT1oHWPcmhvVjuhz95LImcEalC3qcU4M+joMU T0dVtuhn755zg== From: Jeff Layton Date: Fri, 13 Mar 2026 14:45:21 -0400 Subject: [PATCH v2 2/2] EVM: add comment describing why ino field is still unsigned long Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <20260313-iino-u64-v2-2-f9abda2464d5@kernel.org> References: <20260313-iino-u64-v2-0-f9abda2464d5@kernel.org> In-Reply-To: <20260313-iino-u64-v2-0-f9abda2464d5@kernel.org> To: Ryusuke Konishi , Viacheslav Dubeyko , Christian Brauner , Mimi Zohar , Roberto Sassu , Dmitry Kasatkin , Eric Snowberg , Paul Moore , James Morris , "Serge E. Hallyn" Cc: linux-nilfs@vger.kernel.org, linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org, linux-security-module@vger.kernel.org, linux-fsdevel@vger.kernel.org, Jeff Layton X-Mailer: b4 0.14.2 X-Developer-Signature: v=1; a=openpgp-sha256; l=1386; i=jlayton@kernel.org; h=from:subject:message-id; bh=Vytham6oPFTdVP7zlc8wsX2dbeVuNOdhbpe3qUY80eE=; b=owEBbQKS/ZANAwAKAQAOaEEZVoIVAcsmYgBptFtHVGsrqAxYGtXuCQ/JYxGPfWUNgo1lLCSUj /YxSVapIHiJAjMEAAEKAB0WIQRLwNeyRHGyoYTq9dMADmhBGVaCFQUCabRbRwAKCRAADmhBGVaC FX92D/9nua2e1HJ7hFrbi3pC4jkry5qKaxJSkox+XIxiA8MDyoZt64+/KPhETaU4oby4jAT9dJ2 C3Go+zYOdk2t4kKIQ0UkhYEURTLkSW4/Rs8vyt/vchtzt8Fk5VPbY7Jv15rs6pMZLNx1FjZVBuN w7op0eT46v+tiPK3uoRAfE3nZu8bL8BUMriCATH8ySeCQRFiexmRJm2yJBZN1YtB1tgFUvSMfBt 1zYagMr7xuZYGIsDcnYWe0H3ugfyOVB9ayg7c6WsIUwqF4RWxbvkSrLm6PRKSkq9tHgWM0Lwz3I vixeTLgHswtGFp9LohAct1BZA9lyc7o6NGoPt0xSATQdVpAUG8/IBLMryeiGpjJiiDDItDtR9yW f8gTIlz4WOBRUkAOD9tmtf/nyOC4z1jve/OGROLXvmNVh3wPr/sC4tlV6oEegioOGEkhikEsq9a t/PsX86yAyGvcDhBSz8Uv4+oo5jmIWaKVwXkPrommyaeglc45/RrrUj2fM6Nwrh39tTfhhOTbZV FIOkr67djnn41oHUqn3DRTWvUovkCp8Y79PycPOxGeQOGVwikyV+seLXezk1nvAb6GvVQ9c0Obr GZbgFsvnmocoGQtt0xk3n/lK+1nLSDf/QgDxig1O0pj8+RHxWvlRefaiR9IClqgJUQQ0sSghyi5 zUdFI6+aED4iOCQ== X-Developer-Key: i=jlayton@kernel.org; a=openpgp; fpr=4BC0D7B24471B2A184EAF5D3000E684119568215 Mimi pointed out that we didn't widen the inode number field in struct h_misc alongside the inode->i_ino widening. While we could make an equivalent change there, that would require EVM resigning on all 32-bit hosts. Instead, leave the field as an unsigned long. This should have no effect on 64-bit hosts, and allow things to continue working on 32-bit hosts in the cases where the i_ino fits in 32-bits. Add a comment explaining why it's being left as unsigned long. Cc: Mimi Zohar Signed-off-by: Jeff Layton Reviewed-by: Mimi Zohar --- security/integrity/evm/evm_crypto.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/security/integrity/evm/evm_crypto.c b/security/integrity/evm/e= vm_crypto.c index c0ca4eedb0fe5d5c30f45f515a4bc90248ec64ea..1c41af2f91a60a714878ff93b55= 4c90e45546503 100644 --- a/security/integrity/evm/evm_crypto.c +++ b/security/integrity/evm/evm_crypto.c @@ -144,6 +144,12 @@ static void hmac_add_misc(struct shash_desc *desc, str= uct inode *inode, char type, char *digest) { struct h_misc { + /* + * Although inode->i_ino is now u64, this field remains + * unsigned long to allow existing HMAC and signatures from + * 32-bit hosts to continue working when i_ino hasn't changed + * and fits in a u32. + */ unsigned long ino; __u32 generation; uid_t uid; --=20 2.53.0