| Message ID | 20261002223705.2175542-11-aalbersh@kernel.org |
|---|---|
| State | Not Applicable |
| Headers | show
Return-Path: <SRS0=y4U/=HY=vger.kernel.org=linux-ext4+bounces-19951-patchwork-incoming=ozlabs.org@ozlabs.org> X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@legolas.ozlabs.org Authentication-Results: legolas.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=laeAvlxH; dkim-atps=neutral Authentication-Results: legolas.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=ozlabs.org (client-ip=2404:9400:2221:ea00::3; helo=mail.ozlabs.org; envelope-from=srs0=y4u/=hy=vger.kernel.org=linux-ext4+bounces-19951-patchwork-incoming=ozlabs.org@ozlabs.org; receiver=patchwork.ozlabs.org) Received: from mail.ozlabs.org (mail.ozlabs.org [IPv6:2404:9400:2221:ea00::3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519) (No client certificate requested) by legolas.ozlabs.org (Postfix) with ESMTPS id 4hxNx63V2bz1xyX for <incoming@patchwork.ozlabs.org>; Sat, 03 Oct 2026 08:38:50 +1000 (AEST) Received: from mail.ozlabs.org (mail.ozlabs.org [IPv6:2404:9400:2221:ea00::3]) by gandalf.ozlabs.org (Postfix) with ESMTP id 4hxNwT63TXz4w1S for <incoming@patchwork.ozlabs.org>; Sat, 03 Oct 2026 08:38:17 +1000 (AEST) Received: by gandalf.ozlabs.org (Postfix) id 4hxNwT61QFz4w9g; Sat, 03 Oct 2026 08:38:17 +1000 (AEST) Delivered-To: patchwork-incoming@ozlabs.org Authentication-Results: gandalf.ozlabs.org; arc=pass smtp.remote-ip=172.105.105.114 arc.chain=subspace.kernel.org ARC-Seal: i=2; a=rsa-sha256; d=ozlabs.org; s=201707; t=1790980697; cv=pass; b=d+qT7ZVqvzSYygDCOf7oal36QQsy54ab4LSYkkX8KUP03rY+pMNYw1uPmzEBPMTQaDYmKyLHefCiYwpY06fT47YI3jbRuIPlc3K4XEqPjJESJbX+7IFUQsGdZQLq1shyukD16fcVEzMygX4FkM+2VDEmPj9ipCteDdqIgm480L/+SX0Qf4PRqYX5v9xcXnoeUXIgagXL56h/CKcKgnMYEPRQuko/DxrCvt6Vx4Dwyk4uhdUpTtA+Akn5/q3TCp8NO9g+Zjp8SWuyrGiDP6f6BSqLYLykPO/l/YUTpU5hAGyeAy6zhfTg5xiL5iyVpRcElazw5m1HpgLyr3wJqnooAw== ARC-Message-Signature: i=2; a=rsa-sha256; d=ozlabs.org; s=201707; t=1790980697; c=relaxed/relaxed; bh=ieVuD4QM5J41nXjMBZicua2S6B/WM0wDRAu86VZATUA=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=KTh+vCE/NXIX1EUAEA/+1Nwf+yODp+VbLdB0NyRR5qpKWo06ycFLlacf/apBV+W5LuCdTelO5HACeM4Bl8UbAvYfYMpNN+x9yaxpntnMyMXXd4XpsCQX1GO8X4QQTLsK2n0IGZjNaLyNj9kS1FjUVmmI3gIG1bQj1YJEemSHGAfBZy132BNLd+5i32vKxefz46zzuTzHP3aT7skJC6bR17TsaElp6dZ99uHkyLzH3UqhyOIEhxJbBUBNyUWvVuuFIgymp4TSxKBGPDNR3B8L8kBkkrrgvn75AviK7c9R6iDRy/vunCC/25aa3sK2pUmsVkFRD01djFTF3embG/tzIQ== ARC-Authentication-Results: i=2; gandalf.ozlabs.org; dmarc=pass (p=quarantine dis=none) header.from=kernel.org; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=laeAvlxH; dkim-atps=neutral; spf=pass (client-ip=172.105.105.114; helo=tor.lore.kernel.org; envelope-from=linux-ext4+bounces-19951-patchwork-incoming=ozlabs.org@vger.kernel.org; receiver=ozlabs.org) smtp.mailfrom=vger.kernel.org Authentication-Results: gandalf.ozlabs.org; dmarc=pass (p=quarantine dis=none) header.from=kernel.org Authentication-Results: gandalf.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=laeAvlxH; dkim-atps=neutral Authentication-Results: gandalf.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=vger.kernel.org (client-ip=172.105.105.114; helo=tor.lore.kernel.org; envelope-from=linux-ext4+bounces-19951-patchwork-incoming=ozlabs.org@vger.kernel.org; receiver=ozlabs.org) Received: from tor.lore.kernel.org (tor.lore.kernel.org [172.105.105.114]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519) (No client certificate requested) by gandalf.ozlabs.org (Postfix) with ESMTPS id 4hxNwQ1M8jz4w1S for <patchwork-incoming@ozlabs.org>; Sat, 03 Oct 2026 08:38:14 +1000 (AEST) Received: from smtp.subspace.kernel.org (conduit.subspace.kernel.org [100.90.174.1]) by tor.lore.kernel.org (Postfix) with ESMTP id D164431544 for <patchwork-incoming@ozlabs.org>; Fri, 2 Oct 2026 22:37:50 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 93BE846E017; Fri, 2 Oct 2026 22:37:49 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="laeAvlxH" X-Original-To: linux-ext4@vger.kernel.org Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 5AAD044AB68; Fri, 2 Oct 2026 22:37:48 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790980669; cv=none; b=qMO2uG/KoLN9vMEy4eI3EXnohJyBsP2mXhs+20jo7s+Si94EBXXhg+/eiq/KYrUwB87rpCCEheT/DDRZ0UnACtJ1tto9BIhIBRiBTcquU0z+DNgJKnX0jJtDzL4DR3CasE0f6sjnP9MkBq6MdR9XXu1ms5YBTHDoS1Lce/H2PCA= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790980669; c=relaxed/simple; bh=kI3gumtKLRQWMTMAXEpDV7dndwtPFc184oyMWIaFzT8=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=HEps0uxykNpvfiJ/w3QpqXJQD0HVZDq/Uz4Y4BQVpVgE/SN/qYflyakfgjykFEfW63twzGwz861035yX6sY7eealhyISK7b22LF4SzKf3+vJwZ0TrtBNQAhnn4FIoXX6+OiYhNdZE7W04eB/Yb0fo0EiSjCWHe8+QWaC0bFz2XM= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=laeAvlxH; arc=none smtp.client-ip=100.103.45.18 Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0F7D11F000FF; Fri, 2 Oct 2026 22:37:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1790980668; bh=ieVuD4QM5J41nXjMBZicua2S6B/WM0wDRAu86VZATUA=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=laeAvlxHHeZ6Gte499h9yTtQJvpFgsdWN+gvKWUOCNP7KOHdNtYZMYj3fwWTfNjXr pq8f2uFqJbR1EKTTKCOKIYg4ZJzzWY1xpfXeMtssLVo+ORkuobos6oJOSbPBSjXp1J o++FLhVXeMGL3o4k74vh+VS7vftXkT/xXEnoBM9lWPgEFxsN2pzyTDdRgLCpjYXZBY RsFt2zuA1HMsR3ErbZ6Tl7OGqvcRwmsCEe5jnFsaVRnlmJJHk5XEL4Lfodf3xOToi3 Z786P3kwJBXjGqxIN6vxA95vzkKiO83v3Ljg2UwEAcSvAjWx9Flk3oavfJibauapaQ htYUNR0YTBuUQ== From: Andrey Albershteyn <aalbersh@kernel.org> To: djwong@kernel.org, ebiggers@kernel.org, hch@lst.de, Carlos Maiolino <cem@kernel.org> Cc: Andrey Albershteyn <aalbersh@kernel.org>, fsverity@lists.linux.dev, linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org, linux-unionfs@vger.kernel.org, linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-btrfs@vger.kernel.org, david@fromorbit.com Subject: [PATCH v17 10/21] xfs: don't report dio_mem_align and dio_offset_align for fsverity files Date: Sat, 3 Oct 2026 00:36:51 +0200 Message-ID: <20261002223705.2175542-11-aalbersh@kernel.org> X-Mailer: git-send-email 2.54.0 In-Reply-To: <20261002223705.2175542-1-aalbersh@kernel.org> References: <20261002223705.2175542-1-aalbersh@kernel.org> Precedence: bulk X-Mailing-List: linux-ext4@vger.kernel.org List-Id: <linux-ext4.vger.kernel.org> List-Subscribe: <mailto:linux-ext4+subscribe@vger.kernel.org> List-Unsubscribe: <mailto:linux-ext4+unsubscribe@vger.kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-3.8 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DMARC_PASS,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_PASS autolearn=disabled version=4.0.1 X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on gandalf.ozlabs.org |
| Series |
fs-verity support for XFS with post EOF merkle tree
|
expand
|
> Sashiko.dev reported that while fsverity files falls back to the > buffered IO for Direct I/O, they should not report non-zero values in > dio_mem_align and dio_offset_align, meaning it's not supported. > > The STATX_DIOALIGN | STATX_DIO_READ_ALIGN flags are used to explicitly > report if DIO is supported or not. They can not indicate that fallback > to the buffered IO is used in this case. The zero alignment values also > mean that DIO is not supported on this file, see statx(2). > > Signed-off-by: Andrey Albershteyn <aalbersh@kernel.org> Sashiko has reviewed this patch and found no issues. It looks great!
diff --git a/fs/xfs/xfs_iops.c b/fs/xfs/xfs_iops.c index b07ca2a33c64..d9c25c06cc60 100644 --- a/fs/xfs/xfs_iops.c +++ b/fs/xfs/xfs_iops.c @@ -35,6 +35,7 @@ #include <linux/security.h> #include <linux/iversion.h> #include <linux/fiemap.h> +#include <linux/fsverity.h> /* * Directories have different lock order w.r.t. mmap_lock compared to regular @@ -579,6 +580,10 @@ xfs_report_dioalign( struct block_device *bdev = target->bt_bdev; stat->result_mask |= STATX_DIOALIGN | STATX_DIO_READ_ALIGN; + + if (fsverity_active(VFS_I(ip))) + return; + stat->dio_mem_align = bdev_dma_alignment(bdev) + 1; /*