From: Namjae Jeon <linkinjeon@kernel.org>
To: Chen Li <chenli@uniontech.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Sungjong Seo <sj1557.seo@samsung.com>,
Namjae Jeon <namjae.jeon@samsung.com>
Subject: Re: [PATCH] exfat: avoid incorrectly releasing for root inode
Date: Sat, 12 Jun 2021 09:57:16 +0900 [thread overview]
Message-ID: <CAKYAXd_dDQATXMqZ1P6tMSFDR22X55uBvcNtDFSbJQafyT7Ogg@mail.gmail.com> (raw)
In-Reply-To: <87a6nz4s0o.wl-chenli@uniontech.com>
2021-06-09 12:48 GMT+09:00, Chen Li <chenli@uniontech.com>:
>
> In d_make_root, when we fail to allocate dentry for root inode,
> we will iput root inode and returned value is NULL in this function.
>
> So we do not need to release this inode again at d_make_root's caller.
>
> Signed-off-by: Chen Li <chenli@uniontech.com>
merged into #dev, Thanks for your patch!
prev parent reply other threads:[~2021-06-12 0:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 3:48 [PATCH] exfat: avoid incorrectly releasing for root inode Chen Li
2021-06-12 0:57 ` Namjae Jeon [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=CAKYAXd_dDQATXMqZ1P6tMSFDR22X55uBvcNtDFSbJQafyT7Ogg@mail.gmail.com \
--to=linkinjeon@kernel.org \
--cc=chenli@uniontech.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=sj1557.seo@samsung.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;
as well as URLs for NNTP newsgroup(s).