From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from cvsmtppost25.nm.naver.com (cvsmtppost25.nm.naver.com [114.111.35.36]) (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 6254D380FC8 for ; Sat, 1 Aug 2026 06:37:46 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=114.111.35.36 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785566270; cv=none; b=UZU7yH+vxHoORbo+7dohIrMbc6+wHk/hHmNnnnJ53Rx6t54GjXIHqej1Dz4E6so6cGUsW03HGLDtC/UxaVUkBPxYrRfdU0LWej2DQesEUvJ/X3C+DKxe3aH67kvqrCvdIrtQchuX8xV04/PSJk/tMq/EAw0kbN2/0hlexLuN76Q= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785566270; c=relaxed/simple; bh=QLx7gXdPw2Dei/WHKOJ8TTMNtiWbnnKqMyOJo7m0Ai0=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=H0RMEPKjwUdm+RUSbcUpcfx1nN4uE9HIeF6ll9GESMIlbEYO+mnnjT1osRLnjPf9EijhaA3tEEX53mqz1L1yik13fUDgvzeunmZaLV3XDl1s6f+HhKBH1LnQelj7nmqjj99nv8a6bfcBytz8tzEMsNigj3QSfm1OUYhxiFmHybc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=naver.com; spf=pass smtp.mailfrom=naver.com; dkim=pass (2048-bit key) header.d=naver.com header.i=@naver.com header.b=eh0Fsg4g; arc=none smtp.client-ip=114.111.35.36 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=naver.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=naver.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=naver.com header.i=@naver.com header.b="eh0Fsg4g" Received: from cvsendbo029.nm ([10.112.18.60]) by cvsmtppost25.nm.naver.com with ESMTP id TD5a+CinSpOakJOUI3CuiQ for ; Sat, 01 Aug 2026 06:27:36 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=naver.com; s=s20171208; t=1785565656; bh=QLx7gXdPw2Dei/WHKOJ8TTMNtiWbnnKqMyOJo7m0Ai0=; h=From:To:Subject:Date:Message-ID:From:Subject:Feedback-ID: X-Works-Security; b=eh0Fsg4gDq1/uRk7jgVqXXy6ODcAXi8PinI9491Gy0lojEAlEuN8B2mMemgF7W00+ ZojBwYrUHS64/QeUMH3f02jF3RN2ZIaZsd8P9wFON44uc7vC5nZqj2FDc84O1FlsZX CTekGtEVJUv65SgdfI29op+8vX89idr4fD2JTFJDscUKG9HmojUfVFphupPmC5M0Z2 YyRecdG3Q5IYZltSxBPbeha6AtwH6JSimqoNkJx8uS8/ZDX3xY8d2M4G0Ua7qSp0vI +W/yEGul322hfOPDytgxcUPlFeBW5A2Ql/7EfCoqke9U4oF+rNTCBdhGxB2wsxJpd5 goiTmVHwz9wZQ== X-Session-ID: TdGbUKsCQEWfTl5myllVlA X-Works-Send-Opt: rP+8W4eXjHwYKBm9FAF9FNmwKo2mKqErKqb/jJIFjAJYKg== X-Works-Smtp-Source: eqKqFxE/FqJZ+HmrFxUq+6E= Received: from bl4ckhyun.localdomain ([211.41.193.194]) by cvnsmtp008.nm.naver.com with ESMTP id TdGbUKsCQEWfTl5myllVlA for (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384); Sat, 01 Aug 2026 06:27:36 -0000 From: Hyeontae Lee To: linkinjeon@kernel.org Cc: hyc.lee@gmail.com, zzzccc427@gmail.com, baijiaju1990@gmail.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Hyeontae Lee Subject: Re: [PATCH] ntfs: serialize the resident read iomap path with mrec_lock Date: Sat, 1 Aug 2026 15:27:05 +0900 Message-ID: <20260801062705.48184-1-wonju345@naver.com> X-Mailer: git-send-email 2.43.0 In-Reply-To: References: <20260725042421.109599-1-wonju345@naver.com> <20260731091035.28929-1-wonju345@naver.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Hi Namjae, You are right - my version drops the lock before the iomap core copies from iomap->inline_data, so the copy itself was still unprotected. I tested your patch and it fixes the issue: KCSAN, two runs of 180 seconds each on the same reproducer: run 1: 206,015 read faults, 415,351 link/unlink cycles run 2: 205,732 read faults, 421,672 link/unlink cycles No data-race reports in ntfs_attr_find(), ntfs_attr_value_is_valid() or ntfs_read_iomap_begin_resident(), and no "is corrupt" messages. Before the fix the same reproducer produced 40 reports in about one second. PROVE_LOCKING, 60 seconds with the same reproducer: 1,199,159 read faults, 1,396,557 link/unlink cycles, no lockdep splat. Mount, read, write and unmount all behave normally. Tested-by: Hyeontae Lee Thanks, Hyeontae