From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Frank Li <Frank.li@oss.nxp.com>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>
Subject: Re: [PATCH v1 1/1] dmaengine: acpi: Free resource list at appropriate time
Date: Thu, 18 Jun 2026 09:34:48 +0300 [thread overview]
Message-ID: <ajORiHmedgWiT64Z@ashevche-desk.local> (raw)
In-Reply-To: <ajMI-QgrEREC6OTD@lizhi-Precision-Tower-5810>
On Wed, Jun 17, 2026 at 04:52:09PM -0400, Frank Li wrote:
> On Wed, Jun 17, 2026 at 11:14:21AM +0200, Andy Shevchenko wrote:
> > In one case we don't free resources when formally should, and
> > in the other we do unneeded "double free" (emptying an empty
> > list).
> >
> > Both are not critical issues at all, they just make code robust
> > against any possible future changes in the flow.
>
> what are you talking about, can use straight forward words.
>
> You just move acpi_dev_free_resource_list() after check return value
> of acpi_dev_get_resources().
Not really. There are _two_ cases. And while they are slightly different,
the solution is to make them behave in the same ways.
...
> > INIT_LIST_HEAD(&resource_list);
> > ret = acpi_dev_get_resources(adev, &resource_list, NULL, NULL);
> > - if (ret <= 0)
> > + if (ret < 0)
> > return 0;
>
> Dose this change related with this patch?
Yes. It's mentioned in the very first part of the first sentence in the commit
message.
> >
> > list_for_each_entry(rentry, &resource_list, node) {
> > @@ -370,10 +370,11 @@ struct dma_chan *acpi_dma_request_slave_chan_by_index(struct device *dev,
> > INIT_LIST_HEAD(&resource_list);
> > ret = acpi_dev_get_resources(adev, &resource_list,
> > acpi_dma_parse_fixed_dma, &pdata);
> > - acpi_dev_free_resource_list(&resource_list);
> > if (ret < 0)
> > return ERR_PTR(ret);
> >
> > + acpi_dev_free_resource_list(&resource_list);
> > +
> > if (dma_spec->slave_id < 0 || dma_spec->chan_id < 0)
> > return ERR_PTR(-ENODEV);
> >
> > --
> > 2.50.1
> >
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-06-18 6:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 9:14 [PATCH v1 1/1] dmaengine: acpi: Free resource list at appropriate time Andy Shevchenko
2026-06-17 20:52 ` Frank Li
2026-06-18 6:34 ` Andy Shevchenko [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=ajORiHmedgWiT64Z@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=Frank.Li@kernel.org \
--cc=Frank.li@oss.nxp.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@kernel.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