mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Zhan Xusheng <zhanxusheng1024@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, Zhan Xusheng <zhanxusheng@xiaomi.com>
Subject: Re: [PATCH] fs/ntfs3: fix potential double iput on d_make_root() failure
Date: Tue, 7 Apr 2026 19:23:13 +0200	[thread overview]
Message-ID: <e214f99e-b321-4678-916f-778b00985d4e@paragon-software.com> (raw)
In-Reply-To: <20260326091232.92760-1-zhanxusheng@xiaomi.com>

On 3/26/26 10:12, Zhan Xusheng wrote:

> [You don't often get email from zhanxusheng1024@gmail.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> d_make_root() consumes the reference to the passed inode: it either
> attaches it to the newly created dentry on success, or drops it via
> iput() on failure.
>
> In the error path, the code currently does:
>      sb->s_root = d_make_root(inode);
>      if (!sb->s_root)
>          goto put_inode_out;
>
> which leads to a second iput(inode) in put_inode_out. This results in
> a double iput and may trigger a use-after-free if the inode gets freed
> after the first iput().
>
> Fix this by jumping directly to the common cleanup path, avoiding the
> extra iput(inode).
>
> Signed-off-by: Zhan Xusheng <zhanxusheng@xiaomi.com>
> ---
>   fs/ntfs3/super.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ntfs3/super.c b/fs/ntfs3/super.c
> index 174a7cb202a0..d0dad15076ca 100644
> --- a/fs/ntfs3/super.c
> +++ b/fs/ntfs3/super.c
> @@ -1673,7 +1673,7 @@ static int ntfs_fill_super(struct super_block *sb, struct fs_context *fc)
>          sb->s_root = d_make_root(inode);
>          if (!sb->s_root) {
>                  err = -ENOMEM;
> -               goto put_inode_out;
> +               goto out;
>          }
>
>          if (boot2) {
> --
> 2.43.0
>
Hello,

Thanks for the patch. It was applied.
I'm going to take a closer look at this problem.

Regards,
Konstantin


      parent reply	other threads:[~2026-04-07 17:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26  9:12 Zhan Xusheng
2026-04-04 16:19 ` Al Viro
2026-04-07 17:23 ` 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=e214f99e-b321-4678-916f-778b00985d4e@paragon-software.com \
    --to=almaz.alexandrovich@paragon-software.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhanxusheng1024@gmail.com \
    --cc=zhanxusheng@xiaomi.com \
    /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®