From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: <shakevsky@berkeley.edu>
Cc: <linux-kernel@vger.kernel.org>, <ntfs3@lists.linux.dev>
Subject: Re: [PATCH] ntfs3: fix INSERT_RANGE for resident data
Date: Wed, 18 Nov 2026 17:47:36 +0100 [thread overview]
Message-ID: <82a1d7b1-5eb9-43c9-a432-5c4054de330e@paragon-software.com> (raw)
In-Reply-To: <20260830-ntfs3-submission-v1-v1-1-08f61d390cd2@berkeley.edu>
On 8/30/26 10:59, Alon Shakevsky via B4 Relay wrote:
> From: Alon Shakevsky <shakevsky@berkeley.edu>
>
> attr_insert_range() grows a resident data attribute before creating the
> hole. It then moves data with:
>
> memmove(data + bytes, data, bytes);
>
> The move starts at offset zero and copies the insertion length. It should
> start at vbo and copy the bytes between vbo and the old end of the value. A
> valid insertion can therefore write past the MFT record allocation. KASAN
> reports a slab out-of-bounds write in attr_insert_range().
>
> attr_set_size() also sets i_size to the expanded size. The resident path
> adds the insertion length again after the copy. If attr_set_size() converts
> the value to nonresident storage, attr_insert_range() shifts the cluster
> mapping using the expanded size and then adds the length again. Both paths
> grow the file twice. The conversion path also leaves the original data at
> its old offset.
>
> An unprivileged user who can create files on a writable NTFS3 mount can
> reach the resident path by marking a file sparse while it is empty, writing
> resident data, and calling FALLOC_FL_INSERT_RANGE.
>
> Before resizing a resident value, check whether the expanded value will fit
> in its MFT record. If it fits, move the data from vbo, clear the new range,
> and keep the size set by attr_set_size(). Otherwise, return
> E_NTFS_NONRESIDENT so ntfs_fallocate() converts the original value before
> retrying the insertion.
>
> The new conversion path can fail while writing the cached data through its
> new mapping. Update i_blocks and mark the inode dirty in
> attr_force_nonresident() so the converted attribute does not leave stale
> inode accounting.
>
> Fixes: aa30eccb24e5 ("fs/ntfs3: Fallocate (FALLOC_FL_INSERT_RANGE) implementation")
> Cc: stable@vger.kernel.org
> Assisted-by: Antiproof:GPT-5.6-Sol
> Signed-off-by: Alon Shakevsky <shakevsky@berkeley.edu>
> ---
> fs/ntfs3/attrib.c | 42 ++++++++++++++++++++++++------------------
> fs/ntfs3/file.c | 17 +++++++++++++++++
> 2 files changed, 41 insertions(+), 18 deletions(-)
>
> diff --git a/fs/ntfs3/attrib.c b/fs/ntfs3/attrib.c
> index b1c315206ffa..a16e0c259ab1 100644
> --- a/fs/ntfs3/attrib.c
> +++ b/fs/ntfs3/attrib.c
> @@ -2589,35 +2589,37 @@ int attr_insert_range(struct ntfs_inode *ni, u64 vbo, u64 bytes)
> down_write(&ni->file.run_lock);
>
> if (!attr_b->non_res) {
> + char *data;
> + u32 used = le32_to_cpu(mi_b->mrec->used);
> + u64 dsize;
> +
> + dsize = ALIGN(data_size + bytes, 8) - ALIGN(data_size, 8);
> + if (used + dsize > sbi->max_bytes_per_attr) {
> + err = E_NTFS_NONRESIDENT;
> + goto out;
> + }
> +
> err = attr_set_size(ni, ATTR_DATA, ni->file.ads.name,
> ni->file.ads.len, run, data_size + bytes,
> NULL, false);
> + if (err)
> + goto out;
>
> le_b = NULL;
> attr_b = ni_find_attr(ni, NULL, &le_b, ATTR_DATA,
> ni->file.ads.name, ni->file.ads.len, NULL,
> &mi_b);
> - if (!attr_b) {
> + if (!attr_b || attr_b->non_res) {
> err = -EINVAL;
> goto bad_inode;
> }
>
> - if (err)
> - goto out;
> -
> - if (!attr_b->non_res) {
> - /* Still resident. */
> - char *data = Add2Ptr(attr_b,
> - le16_to_cpu(attr_b->res.data_off));
> -
> - memmove(data + bytes, data, bytes);
> - memset(data, 0, bytes);
> - goto done;
> - }
> -
> - /* Resident file becomes nonresident. */
> - data_size = le64_to_cpu(attr_b->nres.data_size);
> - alloc_size = le64_to_cpu(attr_b->nres.alloc_size);
> + data = resident_data(attr_b);
> + memmove(data + vbo + bytes, data + vbo, data_size - vbo);
> + memset(data + vbo, 0, bytes);
> + if (vbo <= ni->i_valid)
> + ni->i_valid += bytes;
> + goto out;
> }
>
> /*
> @@ -2716,7 +2718,6 @@ int attr_insert_range(struct ntfs_inode *ni, u64 vbo, u64 bytes)
> attr_b->nres.valid_size = cpu_to_le64(ni->i_valid);
> mi_b->dirty = true;
>
> -done:
> i_size_write(&ni->vfs_inode, ni->vfs_inode.i_size + bytes);
> ni->ni_flags |= NI_FLAG_UPDATE_PARENT;
> mark_inode_dirty(&ni->vfs_inode);
> @@ -2807,6 +2808,11 @@ int attr_force_nonresident(struct ntfs_inode *ni)
> le32_to_cpu(attr->res.data_size),
> &ni->file.run, &attr, NULL);
> up_write(&ni->file.run_lock);
> + if (!err) {
> + inode_set_bytes(&ni->vfs_inode, attr_ondisk_size(attr));
> + ni->ni_flags |= NI_FLAG_UPDATE_PARENT;
> + mark_inode_dirty(&ni->vfs_inode);
> + }
>
> return err;
> }
> diff --git a/fs/ntfs3/file.c b/fs/ntfs3/file.c
> index 2abf334bfa0c..e11b17f14087 100644
> --- a/fs/ntfs3/file.c
> +++ b/fs/ntfs3/file.c
> @@ -617,6 +617,23 @@ static long ntfs_fallocate(struct file *file, int mode, loff_t vbo, loff_t len)
> ni_lock(ni);
> err = attr_insert_range(ni, vbo, len);
> ni_unlock(ni);
> + if (err == E_NTFS_NONRESIDENT) {
> + ni_lock(ni);
> + err = attr_force_nonresident(ni);
> + ni_unlock(ni);
> + if (err)
> + goto out;
> +
> + err = filemap_write_and_wait_range(mapping, vbo_down,
> + LLONG_MAX);
> + if (err)
> + goto out;
> + truncate_pagecache(inode, vbo_down);
> +
> + ni_lock(ni);
> + err = attr_insert_range(ni, vbo, len);
> + ni_unlock(ni);
> + }
> if (err)
> goto out;
> } else {
>
> ---
> base-commit: 08dbfad3f5040f5bdb6c529da20d6d4e81fefd72
> change-id: 20260830-ntfs3-submission-v1-922a1af22503
>
> Best regards,
> --
> Alon Shakevsky <shakevsky@berkeley.edu>
Hello,
Sorry for the delay.
The patch was applied, thank you.
Regards,
Konstantin
prev parent reply other threads:[~2026-11-18 16:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 8:59 Alon Shakevsky via B4 Relay
2026-11-18 16:47 ` Konstantin Komarov [this message]
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=82a1d7b1-5eb9-43c9-a432-5c4054de330e@paragon-software.com \
--to=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=shakevsky@berkeley.edu \
/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®