From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=91.218.175.172 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1794796038; b=zql7Upgehf1lc4wCka6XjI2sKZfBuUHDxEK3JYzbLrHUg3RpckfGvPUY2he2hnC2bwYD lRUIYu0VbCZZ3i2RegYP2iQyVQfM5EHrE1EyTHojJoLJAr5NiJKawwIN0RYm1QSEVU9lr UaWHVc96SALVr9vChXlj9emr/qK/U77270WB+ScwcPbGoCt6jXDg1vShEZxdM96WTKcpB 6z/4hUP6NQ3jukO+8fMCNscKFYwMAyTNC4fMLF4d3p8UcYd6inYvQq/o54WFXIGwFsl1o ev8gt4qsTYa50XSwKla5vr92paSZqG5BdDtNOz6d4sq98zSJQQWxSX1MP3nxMrcvsDA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1794796038; h=DMARC-Filter:X-Envelope-To:DKIM-Signature:X-Envelope-To:Received: X-Mizu-Trace-ID:X-Migadu-Flow:Date:From:To:Cc:Subject:Message-ID: MIME-Version:Content-Type:Content-Disposition; bh=Xa+s8rck0hvVYXsD+lL/I9md5BKO0hs1gcPH9kuiMFs=; b=R31g3NiYDxtkV5CQUjKBqNEDVQL/7x0nNxF9yAg3uqlWnOQrdObidJl8PUHfiVwTG971 MN9IIIuJV63Sqvz+aA1G+nL46/Qj1eNkwVHSTfO3E+ec4flrbQdUA1n8lAMmCYqA7wWoN FZC/fWH2VRhEaDUiRk26FAFIt8rZ0XDzPa9682hDIhHeAbPF5BWxGEPak241e3JxIwvc2 mi0GTJT5Uxg+8iPy2l3yvta4PoMopdrzJD+dLixngV9NdwsC5poxT5TZwoJ738Z82Qzgf oDHQ5pjJbUJ6pgFuyFkNgkiuIwbaZHl9GlvXTCGJB9GUx0lHTyP28JqnzaOkm05hJlA== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass header.d=linux.dev header.i=@linux.dev header.a=rsa-sha256 header.s=key1 header.b=tliFr88t; arc=none smtp.remote-ip=91.218.175.172 Received: from mta0.migadu.com (out-172.mta0.migadu.com [91.218.175.172]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4BC2C606A31F for ; Mon, 16 Nov 2026 02:27:16 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org 4BC2C606A31F Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key, unprotected) header.d=linux.dev header.i=@linux.dev header.a=rsa-sha256 header.s=key1 header.b=tliFr88t X-Envelope-To: linux-ext4@vger.kernel.org DKIM-Signature: a=rsa-sha256; bh=Xa+s8rck0hvVYXsD+lL/I9md5BKO0hs1gcPH9kuiMFs=; c=simple/simple; d=linux.dev; h=from:to:subject:date:message-id:mime-version:content-type; s=key1; t=1794796035; v=1; x=1795400835; b=tliFr88tkGzfG0yLqb7kDYZly2YmYl8MdwxWzXX53WsrZRQT8OJH9TVbgwLHGreMouhiaYJs LC0VfAAgRIozU6xdZpjQoJyl/oqZPw06SQ7lneqDdQEjMD1udTjSKpegaES3kef7mqI2Sw9IJKS BLTfDbOeuYHp75iXnoHOKCzo= X-Envelope-To: linux-ext4@vger.kernel.org Received: by smtp.migadu.com with ESMTPS id bf9aec3d1c6270c4; Mon, 16 Nov 2026 02:27:15 +0000 X-Mizu-Trace-ID: bf9aec3d1c6270c4 X-Migadu-Flow: FLOW_OUT Date: Mon, 16 Nov 2026 02:27:10 +0000 From: "Jose Fernandez (Anthropic)" To: Theodore Ts'o , Zhang Yi Cc: Jan Kara , Baokun Li , Ojaswin Mujoo , Andreas Dilger , "Ritesh Harjani (IBM)" , guolingxing , Josef Bacik , Chris Mason , linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org, regressions@lists.linux.dev Subject: [REGRESSION] ext4: silent data loss when a split at I/O completion gets ENOSPC Message-ID: X-Mailing-List: linux-ext4@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Ojaswin's cover letter [1] explains how, since commit ea96cb5c4ae3 ("ext4: don't split extent before submitting I/O"), the split of an unwritten extent at I/O completion can get ENOSPC. [1] stops the zeroout from hitting other writes in flight, and [2] reports the failed conversion to fsync(). Neither gives the split its block, so data is still lost. LLM agents working with me found that it happens with default options on a filesystem that is not full, and ran the tests. write() and fsync() return success, and after the pages are evicted part of the file reads back as zeros. Under a load built to run the allocator dry (QEMU without KVM), 42 of 72 files lost data at ea96cb5c4ae3, none of 72 at its parent and none of 48 on v6.18.63. On mainline at 23c62304dde2 32 of 72 did. With [1] rebased on it 42 of 72 still did, now as failed conversions in dmesg. With [1] and [2] fsync() failed with ENOSPC on 47 of 72, and the other 25 read back intact. Nothing our agents have tried fixes it fully. I'm reporting this so you are aware of the regression since v7.0. A reproducer is available to the maintainers off-list. [1] https://lore.kernel.org/linux-ext4/20261102-ext4-endio-zero-bug-v1-0-266d2bb9e6dc@linux.ibm.com/ [2] https://lore.kernel.org/linux-ext4/20261101102145.647496-1-guolingxing@tju.edu.cn/ #regzbot introduced: ea96cb5c4ae3