public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: David Hunter <david.hunter.linux@gmail.com>,
	<bhelgaas@google.com>, <linux-pci@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <julia.lawall@inria.fr>,
	<skhan@linuxfoundation.org>, <javier.carrasco.cruz@gmail.com>,
	Rob Herring <robh@kernel.org>
Subject: Re: [PATCH] of.c: replace of_node_put with __free improves cleanup
Date: Wed, 7 Aug 2024 11:47:47 +0100	[thread overview]
Message-ID: <20240807114747.00002fc2@Huawei.com> (raw)
In-Reply-To: <20240801235526.GA129068@bhelgaas>

On Thu, 1 Aug 2024 18:55:26 -0500
Bjorn Helgaas <helgaas@kernel.org> wrote:

> [+cc Rob, Jonathan]
> 
> On Fri, Jul 19, 2024 at 06:38:05PM -0400, David Hunter wrote:
> > The use of the __free function allows the cleanup to be based on scope
> > instead of on another function called later. This makes the cleanup
> > automatic and less susceptible to errors later.
> > 
> > This code was compiled without errors or warnings.  
> 
> I *think* this looks OK, but I'm not comfy with all this scope magic
> yet, so would like Jonathan and/or Rob to take a peek too.

I'm suspicious of usecases where there isn't a constructor / destructor pair.

This is more of a 'steal' the pointer and destroy it pattern.

Also, bug in this case.... see below.

> 
> And is there some way to include a hint here about how to find the
> implicit of_node_put()?  I think it's this from 9448e55d032d ("of: Add
> cleanup.h based auto release via __free(device_node) markings"):
> 
>   +DEFINE_FREE(device_node, struct device_node *, if (_T) of_node_put(_T))

Yes, it's that one.  Makes sense to add a reference to that in the
patch description for these.
> 
> but it did take some looking to find it.
> 
> If it looks good, I'll tweak the commit log to use imperative mood:
> https://chris.beams.io/posts/git-commit/
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=v6.9#n94
> 
> since this technically says what *could* happen but not what the patch
> *does*.
> 
> > Signed-off-by: David Hunter <david.hunter.linux@gmail.com>
> > ---
> >  drivers/pci/of.c | 4 +---
> >  1 file changed, 1 insertion(+), 3 deletions(-)
> > 
> > diff --git a/drivers/pci/of.c b/drivers/pci/of.c
> > index b908fe1ae951..8b150982f5cd 100644
> > --- a/drivers/pci/of.c
> > +++ b/drivers/pci/of.c
> > @@ -616,16 +616,14 @@ int devm_of_pci_bridge_init(struct device *dev, struct pci_host_bridge *bridge)
> >  
> >  void of_pci_remove_node(struct pci_dev *pdev)
> >  {
> > -	struct device_node *np;
> > +	struct device_node *np __free(device_node) = pci_device_to_OF_node(pdev);
> >  
> > -	np = pci_device_to_OF_node(pdev);
> >  	if (!np || !of_node_check_flag(np, OF_DYNAMIC))

Wil now put the node if that second check fails. Didn't do that before
and I'm guessing we shouldn't?  Technically it calls the cleanup
in the !np case but that is fine as we check for NULL pointer.

So I'd leave this particular one alone.

> >  		return;
> >  	pdev->dev.of_node = NULL;
> >  
> >  	of_changeset_revert(np->data);
> >  	of_changeset_destroy(np->data);
> > -	of_node_put(np);
> >  }
> >  
> >  void of_pci_make_dev_node(struct pci_dev *pdev)
> > -- 
> > 2.34.1
> >   


  reply	other threads:[~2024-08-07 10:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-19 22:38 [PATCH] of.c: replace of_node_put with __free improves cleanup David Hunter
2024-08-01 23:55 ` Bjorn Helgaas
2024-08-07 10:47   ` Jonathan Cameron [this message]
2024-08-07 16:18     ` Rob Herring

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=20240807114747.00002fc2@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=bhelgaas@google.com \
    --cc=david.hunter.linux@gmail.com \
    --cc=helgaas@kernel.org \
    --cc=javier.carrasco.cruz@gmail.com \
    --cc=julia.lawall@inria.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=skhan@linuxfoundation.org \
    /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