All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shuhao Fu <sfual@cse.ust.hk>
To: "Yuezhang.Mo@sony.com" <Yuezhang.Mo@sony.com>
Cc: Namjae Jeon <linkinjeon@kernel.org>,
	Sungjong Seo <sj1557.seo@samsung.com>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] exfat: fix refcount leak in exfat_find
Date: Tue, 21 Oct 2025 08:47:12 +0000	[thread overview]
Message-ID: <aPdIkNGpwXwA/SMz@chcpu18> (raw)
In-Reply-To: <PUZPR04MB6316F58807941F86C2769FCC81F2A@PUZPR04MB6316.apcprd04.prod.outlook.com>

On Tue, Oct 21, 2025 at 08:21:57AM +0000, Yuezhang.Mo@sony.com wrote:
> On Tue, Oct 21, 2025 16:04 Shuhao Fu <sfual@cse.ust.hk> wrote:
> > On Tue, Oct 21, 2025 at 01:38:29AM +0000, Yuezhang.Mo@sony.com wrote:
> > > On Mon, Oct 20, 2025 23:00 Shuhao Fu <sfual@cse.ust.hk> wrote:
> > > 
> > > I think it would be better to move these checks after exfat_put_dentry_set().
> > > Because the following check will correct ->valid_size and ->size.
> > > 
> > >         if (!is_valid_cluster(sbi, info->start_clu) && info->size) {
> > >                 exfat_warn(sb, "start_clu is invalid cluster(0x%x)",
> > >                                 info->start_clu);
> > >                 info->size = 0;
> > >                 info->valid_size = 0;
> > >         }
> > > 
> > 
> > Do you mean that we should put these two checks after
> > `exfat_put_dentry_set`, like below?
> > 
> 
> Yes, that's what I mean.
> 

Thank you for your suggestion. Patch v2 has been sent out addressing
your comments.

https://lore.kernel.org/linux-fsdevel/aPdHWFiCupwDRiFM@osx.local/

      reply	other threads:[~2025-10-21  8:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-20 15:00 [PATCH] exfat: fix refcount leak in exfat_find Shuhao Fu
2025-10-21  1:38 ` Yuezhang.Mo
2025-10-21  8:04   ` Shuhao Fu
2025-10-21  8:21     ` Yuezhang.Mo
2025-10-21  8:47       ` Shuhao Fu [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=aPdIkNGpwXwA/SMz@chcpu18 \
    --to=sfual@cse.ust.hk \
    --cc=Yuezhang.Mo@sony.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.