From: Matthias Goergens <matthias.goergens@gmail.com>
To: Namjae Jeon <linkinjeon@kernel.org>, Hyunchul Lee <hyc.lee@gmail.com>
Cc: Baolin Liu <liubaolin@kylinos.cn>,
liubaolin <liubaolin12138@163.com>,
ntfs@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] ntfs: fix spurious EIO and ENOSPC on nearly full volumes
Date: Thu, 1 Oct 2026 22:49:35 +0800 [thread overview]
Message-ID: <cover.1790853718.git.matthias.goergens@gmail.com> (raw)
These fix three errors returned while free space is left. 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. Reproducers, run with KASAN and lockdep:
https://github.com/matthiasgoergens/linux/tree/reproducer/2026-10-01-ntfs-nearfull-v2
Changes in v2: in patch 2, a contiguous request whose run from the hint
stops at the end of a bitmap buffer or of the zone now gets that run
back, instead of a second, non-adjacent run from the zone position, as
Baolin Liu suggested. That second run also happens on ntfs-next
without this series, and fallocate() over a hole then leaves part of the
range reading the data of a deleted file; patch 2 now fixes that as
well. Rebased on ntfs-next, with Baolin's Reviewed-by on patches 1
and 3.
v1: https://lore.kernel.org/all/cover.1790503811.git.matthias.goergens@gmail.com/
Matthias Goergens (3):
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
fs/ntfs/attrlist.c | 5 +++--
fs/ntfs/file.c | 3 ---
fs/ntfs/lcnalloc.c | 25 ++++++++++++++++++++++---
3 files changed, 25 insertions(+), 8 deletions(-)
base-commit: 708f9d56cacae21aeee98d16bcdd50a66edc04a0
--
2.56.0
next reply other threads:[~2026-10-01 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 14:49 Matthias Goergens [this message]
2026-10-01 14:49 ` [PATCH v2 1/3] ntfs: set the attribute list size before reserving space for it Matthias Goergens
2026-10-01 14:49 ` [PATCH v2 2/3] ntfs: restart the zone search when the allocation hint fails Matthias Goergens
2026-10-01 14:49 ` [PATCH v2 3/3] ntfs: do not refuse fallocate() when the MFT zone is empty Matthias Goergens
2026-10-02 5:37 ` [PATCH v2 0/3] ntfs: fix spurious EIO and ENOSPC on nearly full volumes Hyunchul Lee
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.1790853718.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=liubaolin@kylinos.cn \
--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®