From: Greg KH <gregkh@linuxfoundation.org>
To: Tudor.Ambarus@microchip.com
Cc: pavel@ucw.cz, linux-kernel@vger.kernel.org,
dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
dan.j.williams@intel.com, vkoul@kernel.org,
Ludovic.Desroches@microchip.com, stable@vger.kernel.org
Subject: Re: [PATCH 4.19] dmaengine: at_hdmac: Fix memory leak
Date: Mon, 4 Jan 2021 12:02:33 +0100 [thread overview]
Message-ID: <X/L1yZgmni6KHsrL@kroah.com> (raw)
In-Reply-To: <d3a6fa19-0852-92d9-c434-40297edc625a@microchip.com>
On Wed, Sep 23, 2020 at 08:19:18AM +0000, Tudor.Ambarus@microchip.com wrote:
> On 9/23/20 11:13 AM, Tudor.Ambarus@microchip.com wrote:
> > Hi, Pavel,
> >
> > On 9/20/20 11:28 AM, Pavel Machek wrote:
> >> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> >>
> >> This fixes memory leak in at_hdmac. Mainline does not have the same
> >> problem.
> >>
> >> Signed-off-by: Pavel Machek (CIP) <pavel@denx.de>
> >>
> >> diff --git a/drivers/dma/at_hdmac.c b/drivers/dma/at_hdmac.c
> >> index 86427f6ba78c..0847b2055857 100644
> >> --- a/drivers/dma/at_hdmac.c
> >> +++ b/drivers/dma/at_hdmac.c
> >> @@ -1714,8 +1714,10 @@ static struct dma_chan *at_dma_xlate(struct of_phandle_args *dma_spec,
> >> atslave->dma_dev = &dmac_pdev->dev;
> >>
> >> chan = dma_request_channel(mask, at_dma_filter, atslave);
> >> - if (!chan)
> >> + if (!chan) {
> >> + kfree(atslave);
> >> return NULL;
> >> + }
> >
> > Thanks for submitting this to stable. While the fix is good, you can instead
> > cherry-pick the commit that hit upstream. In order to do that cleanly on top
> > of v4.19.145, you have to pick two other fixes:
> >
> > commit a6e7f19c9100 ("dmaengine: at_hdmac: Substitute kzalloc with kmalloc")
> > commit 3832b78b3ec2 ("dmaengine: at_hdmac: add missing put_device() call in at_dma_xlate()")
> > commit a6e7f19c9100 ("dmaengine: at_hdmac: Substitute kzalloc with kmalloc")
>
> this last commit should have been
> commit e097eb7473d9 ("dmaengine: at_hdmac: add missing kfree() call in at_dma_xlate()")
>
> bad copy and paste :)
So are all 3 of those needed on both 5.4.y and 4.19.y to resolve this
issue?
thanks,
greg k-h
next prev parent reply other threads:[~2021-01-04 11:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 8:28 [PATCH 4.19] dmaengine: at_hdmac: Fix memory leak Pavel Machek
2020-09-23 6:39 ` Ludovic Desroches
2020-09-23 8:13 ` Tudor.Ambarus
2020-09-23 8:19 ` Tudor.Ambarus
2021-01-04 11:02 ` Greg KH [this message]
2021-01-05 8:03 ` Tudor.Ambarus
2021-01-06 16:53 ` Greg KH
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=X/L1yZgmni6KHsrL@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Ludovic.Desroches@microchip.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).