From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1794065083; b=YS+f2GMXaJIjKCyL7tHm75CL2ksZQYYgcxdHQ389S/gloUx3YXACPPZ3dGw/A2sGA34J JoDhPxh7w8DBIvUj8D2w9WSnpXS2S4AYTsfZv7qhybMj13VUm8klXmK0owb3DOtHops+u 9HYlEUC6gcR+xg4PEraDbzWpZj12sMLlPEk9B5v7TmyYI2fd44pY66uVsbwTwx40WuKOE 3rGhz1zBWqiOb6dhNkZnna/xDECvz1UGyKQRh8yLztP5qydMWwXvg8ZrGxvNHWgqPPMO8 gAiu7y28pnjm7L45/CrbPkYVYCSl5jcTYchj1Kpsdp973BIzCtYDDrp93l5IyEEGacQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1794065083; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: In-Reply-To:References:User-Agent:X-stable:X-Patchwork-Hint: MIME-Version:Content-Transfer-Encoding; bh=IIREvKIMs981BE2DH7LrnkaTpe8nB/+xhV1nBSYlVP4=; b=y5s7ksfT/Pmkm5/UeujRdQVBy35zmcAHG3VLIi1fNMax4c5pUKpfO9N7N28npFcXIsIu F96ZRbSTvUhqqY2Hj7Wvxsu7xp7FKtgvEysTVYpm3OM0eGUasSPq1HCK+lpa+JR347X8l I3cYbZ24RCXEC/9n213W3kecHO/DUQO1XQU7yZ5pwkgoMHTGNdj0yL1GPef17JAcqhNtS zdwvwP2ZCyk19x0Mf5T+GMYa2cteT7i3WEYJwJ4OEXZD5WrZIfsABwVixnfLgp3M7AAQA qlzM26Cu3gVdcAfXW39WT4JCM1+OhAV1bb4oXmnMR+2UkBBgnrcaq4Q/O3IFqCD1qZA== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=IZfFqXyn; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C9260606A334; Sat, 7 Nov 2026 15:24:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=IZfFqXyn Received: by smtp.kernel.org (Postfix) with ESMTPSA id 705971F0089F; Sat, 7 Nov 2026 15:24:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1794065082; bh=IIREvKIMs981BE2DH7LrnkaTpe8nB/+xhV1nBSYlVP4=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=IZfFqXyn2Gxo6DXxiAYtlGPeR9CdYZqQfyt6NAyxi3g3GlQlogQEhsJEfMIf5yNzs /9DQoeZ3GfZ4hzDy5RTC0oxoiZx30bKtuDM1b5+g0eUALxc6UXNwGIqXAFkXSHPx4e DmoW3qkZj3VzlI9T/CpGGaJrzT+Hb76fsLRUcAnA= From: Greg Kroah-Hartman To: stable@vger.kernel.org Cc: Greg Kroah-Hartman , patches@lists.linux.dev, Hongling Zeng , Hyunchul Lee , Baolin Liu , Namjae Jeon , Sasha Levin Subject: [PATCH 7.3 0918/1257] ntfs: fix volume flag update races Date: Sat, 7 Nov 2026 08:53:34 -0500 Message-ID: <20261107135004.701261508@linuxfoundation.org> X-Mailer: git-send-email 2.56.0 In-Reply-To: <20261107134939.434104957@linuxfoundation.org> References: <20261107134939.434104957@linuxfoundation.org> User-Agent: quilt/0.69 X-stable: review X-Patchwork-Hint: ignore X-Mailing-List: stable@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 7.3-stable review patch. If anyone has any objections, please let me know. ------------------ From: Hongling Zeng [ Upstream commit 56a64ee0f99d4ca1756cf743f951c110d39401e5 ] ntfs_set_volume_flags() and ntfs_clear_volume_flags() both read vol->vol_flags outside any lock to compute the new value before handing it to ntfs_write_volume_flags(), which only takes ni->mrec_lock around the actual write. The read-modify-write is therefore not atomic, and two concurrent callers can lose an update: ntfs_sync_fs() may derive a "clean" value from vol->vol_flags while a writer concurrently records an error and sets VOLUME_IS_DIRTY; the locked write then silently overwrites the freshly-set dirty bit. The on-disk volume looks clean despite the recorded errors, so chkdsk will not run on the next mount and corrupted metadata can persist. Fix by moving the read-modify-write inside the mrec_lock: pass the bits to set and to clear separately, and combine them with the current flag state under the lock inside ntfs_write_volume_flags(). The set/clear helpers pass only the bits to modify, not the complete flag state. The bit manipulation is done on CPU-endian values, and the result is converted back to little-endian before storing it. The wrappers keep their signatures so callers are unchanged. Cc: stable@vger.kernel.org Signed-off-by: Hongling Zeng Reviewed-by: Hyunchul Lee Reviewed-by: Baolin Liu Signed-off-by: Namjae Jeon Signed-off-by: Sasha Levin --- fs/ntfs/super.c | 63 +++++++++++++++++++++++++++++++++++-------------- 1 file changed, 45 insertions(+), 18 deletions(-) diff --git a/fs/ntfs/super.c b/fs/ntfs/super.c index 9f5cf65fd3a55..57584f157f154 100644 --- a/fs/ntfs/super.c +++ b/fs/ntfs/super.c @@ -360,31 +360,45 @@ void ntfs_handle_error(struct super_block *sb) } /* - * ntfs_write_volume_flags - write new flags to the volume information flags + * ntfs_write_volume_flags - apply flag changes to the volume information flags * @vol: ntfs volume on which to modify the flags - * @flags: new flags value for the volume information flags + * @set_bits: bits to set in the volume information flags + * @clear_bits: bits to clear in the volume information flags * * Internal function. You probably want to use ntfs_{set,clear}_volume_flags() * instead (see below). * - * Replace the volume information flags on the volume @vol with the value - * supplied in @flags. Note, this overwrites the volume information flags, so - * make sure to combine the flags you want to modify with the old flags and use - * the result when calling ntfs_write_volume_flags(). + * Combine @set_bits and @clear_bits with the current in-memory flag state and + * write the result back. The set/clear helpers pass only the bits to modify, + * not the complete flag state. The read-modify-write happens under + * ni->mrec_lock so that concurrent set/clear operations cannot lose updates. + * All bit manipulation is done on CPU-endian values, and the result is + * converted back to little-endian before storing it. * * Return 0 on success and -errno on error. */ -static int ntfs_write_volume_flags(struct ntfs_volume *vol, const __le16 flags) +static int ntfs_write_volume_flags(struct ntfs_volume *vol, + const __le16 set_bits, const __le16 clear_bits, + const bool skip_if_errors) { struct ntfs_inode *ni = NTFS_I(vol->vol_ino); struct volume_information *vi; struct ntfs_attr_search_ctx *ctx; + u16 flags; int err; - ntfs_debug("Entering, old flags = 0x%x, new flags = 0x%x.", - le16_to_cpu(vol->vol_flags), le16_to_cpu(flags)); mutex_lock(&ni->mrec_lock); - if (vol->vol_flags == flags) + + if (skip_if_errors && NVolErrors(vol)) + goto done; + + flags = le16_to_cpu(vol->vol_flags); + flags |= le16_to_cpu(set_bits) & le16_to_cpu(VOLUME_FLAGS_MASK); + flags &= ~(le16_to_cpu(clear_bits) & le16_to_cpu(VOLUME_FLAGS_MASK)); + ntfs_debug("Entering, old flags = 0x%x, new flags = 0x%x.", + le16_to_cpu(vol->vol_flags), flags); + + if (le16_to_cpu(vol->vol_flags) == flags) goto done; ctx = ntfs_attr_get_search_ctx(ni, NULL); @@ -400,7 +414,7 @@ static int ntfs_write_volume_flags(struct ntfs_volume *vol, const __le16 flags) vi = (struct volume_information *)((u8 *)ctx->attr + le16_to_cpu(ctx->attr->data.resident.value_offset)); - vol->vol_flags = vi->flags = flags; + vol->vol_flags = vi->flags = cpu_to_le16(flags); mark_mft_record_dirty(ctx->ntfs_ino); ntfs_attr_put_search_ctx(ctx); done: @@ -421,13 +435,14 @@ static int ntfs_write_volume_flags(struct ntfs_volume *vol, const __le16 flags) * @flags: flags to set on the volume * * Set the bits in @flags in the volume information flags on the volume @vol. + * The bits are combined with the current flag state under the lock in + * ntfs_write_volume_flags(), so concurrent updates are not lost. * * Return 0 on success and -errno on error. */ int ntfs_set_volume_flags(struct ntfs_volume *vol, __le16 flags) { - flags &= VOLUME_FLAGS_MASK; - return ntfs_write_volume_flags(vol, vol->vol_flags | flags); + return ntfs_write_volume_flags(vol, flags, 0, false); } /* @@ -436,14 +451,27 @@ int ntfs_set_volume_flags(struct ntfs_volume *vol, __le16 flags) * @flags: flags to clear on the volume * * Clear the bits in @flags in the volume information flags on the volume @vol. + * The bits are combined with the current flag state under the lock in + * ntfs_write_volume_flags(), so concurrent updates are not lost. * * Return 0 on success and -errno on error. */ int ntfs_clear_volume_flags(struct ntfs_volume *vol, __le16 flags) { - flags &= VOLUME_FLAGS_MASK; - flags = vol->vol_flags & cpu_to_le16(~le16_to_cpu(flags)); - return ntfs_write_volume_flags(vol, flags); + return ntfs_write_volume_flags(vol, 0, flags, false); +} + +/* + * ntfs_clear_volume_dirty_if_no_errors - clear dirty bit if no errors exist + * @vol: ntfs volume whose dirty bit should be cleared + * + * Check NVolErrors() and clear VOLUME_IS_DIRTY under the same mrec_lock so + * ntfs_sync_fs() cannot clear the dirty bit after a concurrent error has been + * recorded. + */ +static int ntfs_clear_volume_dirty_if_no_errors(struct ntfs_volume *vol) +{ + return ntfs_write_volume_flags(vol, 0, VOLUME_IS_DIRTY, true); } int ntfs_write_volume_label(struct ntfs_volume *vol, char *label) @@ -1932,8 +1960,7 @@ static int ntfs_sync_fs(struct super_block *sb, int wait) return 0; /* If there are some dirty buffers in the bdev inode */ - if (!NVolErrors(vol) && - ntfs_clear_volume_flags(vol, VOLUME_IS_DIRTY)) { + if (ntfs_clear_volume_dirty_if_no_errors(vol)) { ntfs_warning(sb, "Failed to clear dirty bit in volume information flags. Run chkdsk."); err = -EIO; } -- 2.53.0