From: Matthias Goergens <matthias.goergens@gmail.com>
To: Namjae Jeon <linkinjeon@kernel.org>, Hyunchul Lee <hyc.lee@gmail.com>
Cc: Baolin Liu <liubaolin12138@163.com>,
ntfs@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/4] ntfs: fix spurious EIO and ENOSPC on nearly full volumes
Date: Sun, 4 Oct 2026 17:56:04 +0800 [thread overview]
Message-ID: <cover.1791107674.git.matthias.goergens@gmail.com> (raw)
These fix three errors returned while free space is left, and a
contiguous cluster allocation that comes back in two runs. Patch 1
fixes file creation failing with EIO on a nearly full volume; it now
goes on until the volume is full and then fails with ENOSPC. Patch 2
fixes the cluster allocator missing free clusters when its start hint
lies at or past the end of the volume, which empties the MFT zone, and
patch 3 removes the fallocate() check that then fails every later call.
Together the two bugs make fallocate() refuse space that is free until
the next mount. Patch 4 keeps a contiguous request to a single run:
fallocate() zeroes only the first run, so the clusters of a second one
kept the data of a deleted file. Reproducers, run with KASAN and
lockdep:
https://github.com/matthiasgoergens/linux/tree/reproducer/2026-10-04-ntfs-nearfull-v3
Changes in v3: Namjae Jeon asked whether a contiguous request can still
get a second run once the search has left the hint, for instance when
the run reaches the end of a bitmap page and the next page is skipped as
full. It can, on that path and on two more: where the search wraps to
pass 2, and where it shrinks the MFT zone after trying every zone. On
ntfs-next each left 16 of 20 fallocated clusters reading the data of a
deleted file. New patch 4 does what he suggested: before setting a
cluster's bit, it checks that the cluster follows the run, and returns
the run otherwise. Patches 1 to 3 are unchanged apart from Hyunchul
Lee's Reviewed-by. Rebased on ntfs-next.
v2: https://lore.kernel.org/all/cover.1790853718.git.matthias.goergens@gmail.com/
v1: https://lore.kernel.org/all/cover.1790503811.git.matthias.goergens@gmail.com/
Matthias Goergens (4):
ntfs: set the attribute list size before reserving space for it
ntfs: restart the zone search when the allocation hint fails
ntfs: do not refuse fallocate() when the MFT zone is empty
ntfs: do not give a contiguous cluster allocation a second run
fs/ntfs/attrlist.c | 5 +++--
fs/ntfs/file.c | 3 ---
fs/ntfs/lcnalloc.c | 35 ++++++++++++++++++++++++++++++++---
3 files changed, 35 insertions(+), 8 deletions(-)
base-commit: b2a3b6b6c7b09040e3f44ade6e20a7689e4acd28
--
2.56.0
next reply other threads:[~2026-10-04 9:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 9:56 Matthias Goergens [this message]
2026-10-04 9:56 ` [PATCH v3 1/4] ntfs: set the attribute list size before reserving space for it Matthias Goergens
2026-10-04 9:56 ` [PATCH v3 2/4] ntfs: restart the zone search when the allocation hint fails Matthias Goergens
2026-10-04 9:56 ` [PATCH v3 3/4] ntfs: do not refuse fallocate() when the MFT zone is empty Matthias Goergens
2026-10-04 9:56 ` [PATCH v3 4/4] ntfs: do not give a contiguous cluster allocation a second run Matthias Goergens
2026-10-05 2:26 ` [PATCH v3 0/4] ntfs: fix spurious EIO and ENOSPC on nearly full volumes Namjae Jeon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1791107674.git.matthias.goergens@gmail.com \
--to=matthias.goergens@gmail.com \
--cc=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liubaolin12138@163.com \
--cc=ntfs@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®