From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Dmitry Morgun <d.morgun@ispras.ru>
Cc: <ntfs3@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<lvc-project@linuxtesting.org>
Subject: Re: [PATCH] fs/ntfs3: check return values in indx_delete_entry()
Date: Wed, 7 Oct 2026 23:33:55 +0200 [thread overview]
Message-ID: <4c02fe66-a6b9-4900-a2c9-4a660db263c4@paragon-software.com> (raw)
In-Reply-To: <20260712151549.1781-1-d.morgun@ispras.ru>
On 7/12/26 17:15, Dmitry Morgun wrote:
> When the index tree collapses down to an empty root,
> indx_delete_entry() calls attr_set_size() and ni_remove_attr() for
> both ATTR_ALLOC and ATTR_BITMAP, but their return values are
> overwritten by the following call without being checked.
>
> In most other call sites of these functions the return value is
> checked, so add the same checks here in case an error at this point
> is meaningful.
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> Fixes: 82cae269cfa9 ("fs/ntfs3: Add initialization of super block")
> Signed-off-by: Dmitry Morgun <d.morgun@ispras.ru>
> ---
> fs/ntfs3/index.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/fs/ntfs3/index.c b/fs/ntfs3/index.c
> index 5344b29b0..c730175d7 100644
> --- a/fs/ntfs3/index.c
> +++ b/fs/ntfs3/index.c
> @@ -2619,18 +2619,28 @@ int indx_delete_entry(struct ntfs_index *indx, struct ntfs_inode *ni,
>
> err = attr_set_size(ni, ATTR_ALLOC, in->name, in->name_len,
> &indx->alloc_run, 0, NULL, false);
> + if (err)
> + goto out;
> +
> if (in->name == I30_NAME)
> i_size_write(&ni->vfs_inode, 0);
>
> err = ni_remove_attr(ni, ATTR_ALLOC, in->name, in->name_len,
> false, NULL);
> run_close(&indx->alloc_run);
> + if (err)
> + goto out;
>
> err = attr_set_size(ni, ATTR_BITMAP, in->name, in->name_len,
> &indx->bitmap_run, 0, NULL, false);
> + if (err)
> + goto out;
> +
> err = ni_remove_attr(ni, ATTR_BITMAP, in->name, in->name_len,
> false, NULL);
> run_close(&indx->bitmap_run);
> + if (err)
> + goto out;
>
> root = indx_get_root(indx, ni, &attr, &mi);
> if (!root) {
> --
> 2.34.1
Hello,
Your patch is applied, thank you.
Regards,
Konstantin
prev parent reply other threads:[~2026-10-07 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 15:15 Dmitry Morgun
2026-10-07 21:33 ` 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=4c02fe66-a6b9-4900-a2c9-4a660db263c4@paragon-software.com \
--to=almaz.alexandrovich@paragon-software.com \
--cc=d.morgun@ispras.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=ntfs3@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®