From mboxrd@z Thu Jan 1 00:00:00 1970 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 1B20F4C8C68 for ; Fri, 9 Oct 2026 11:17:58 +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=1791544689; cv=none; b=N1mzNEeysxrZqcxrLxKS2p5iaNCAbChODjtmxW61VK7Qn4qprWGw/jOn8qyMdo7x6hMYP4wsrzx9CKC0+rKc/CGA9suBnZqZZ6DDlPwjqfeB7WfABND9EFLSOufKBPR3QHRr9H4XZ+N18i7J8p7X/BBey149RrgqmfP/hha4+Uk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791544689; c=relaxed/simple; bh=kK4idsUd8lqo167jsOnbtrE5p40U9UGxkV0ayFAYQ0M=; h=Message-ID:From:Subject:To:Cc:In-Reply-To:References:Content-Type: Date; b=AsTzf5++bx4x49fX2SiWhyAfb3uHIg5vFqq8ZueyuEMQTpyK67g+sgbHNcNFJMa9RRR9i6/mFhQL3ZrEBqcWGc8IH/bdVCdFNcQjG53F6XGaE8NI1H52WjvR4u2+JYz4ffflKHA19754SbAZ5lNL/Fldag5YYFrx3CObulDSzho= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=f+iqYN37; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="f+iqYN37" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 435211F000FF; Fri, 9 Oct 2026 11:17:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1791544678; bh=kK4idsUd8lqo167jsOnbtrE5p40U9UGxkV0ayFAYQ0M=; h=From:Subject:Reply-To:To:Cc:In-Reply-To:References:Date; b=f+iqYN37PDtlVZUbuahoC8EGaDnBwj0Ey/Skj7sX6GyLWpKWHpOBFVBUHbBiEK43J 9fBaBkYQ21KV+XDz+d08/GL++ua8rhBaYCCF/acXYs3nYtwzlVm+4lwh29QDun1eRA U5jLbjrixaRqViJaqYZtAiTjEoiWkwspN9yKdKM/gW/dASHZEuT0+IK/DzywSRhZtV XhWXP+BQuMovR8BBEsfjEyGz540IDrFC3vpMilk558JmD18uHv0AfGtk0RYoCiFdSN wwfJMGy98+3p/HyyF0miVtO746kDXTtEalqtZUp4CGF2+GHCKn/2aEXyejeTtzIYlg EQTHlw9ufVRcQ== Message-ID: From: sashiko-bot@kernel.org Subject: Re: [PATCH v7 31/31] ext4: introduce a mount option for iomap buffered I/O path Reply-To: sashiko-reviews@lists.linux.dev To: "Zhang Yi" Cc: linux-ext4@vger.kernel.org, tytso@mit.edu In-Reply-To: <20261009103831.2978767-3-yi.zhang@huaweicloud.com> References: <20261009103033.2920530-1-yi.zhang@huaweicloud.com> <20261009103831.2978767-3-yi.zhang@huaweicloud.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Date: Fri, 09 Oct 2026 11:17:57 +0000 Precedence: bulk X-Mailing-List: linux-ext4@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: > From: Zhang Yi >=20 > Since the iomap buffered I/O path does not yet support all existing ext4 > features, it cannot be enabled by default. Introduce the > 'buffered_iomap' and 'nobuffered_iomap' mount options to explicitly > enable or disable the iomap buffered I/O path for regular files. >=20 > Toggling this option via remount is allowed. The change of I/O path will > not take effect immediately. It will be deferred. The new setting will > only take effect after the inode is re-initialized (i.e., after the last > reference is dropped and the inode is re-read from disk). >=20 > Signed-off-by: Zhang Yi Sashiko has reviewed this patch and found no issues. It looks great! --=20 Sashiko AI review =C2=B7 https://sashiko.dev/#/patchset/20261009103033.2920= 530-1-yi.zhang@huaweicloud.com?part=3D31