mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Tudor.Ambarus@microchip.com>
To: <gregkh@linuxfoundation.org>
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: Tue, 5 Jan 2021 08:03:20 +0000	[thread overview]
Message-ID: <b7747258-80dd-f5bd-6dd3-ea2cf410f86f@microchip.com> (raw)
In-Reply-To: <X/L1yZgmni6KHsrL@kroah.com>

On 1/4/21 1:02 PM, Greg KH wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> 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?
> 

Yes. I've just cherry-picked all three commits on both v5.4.86 and v4.19.164,
everything looks ok. I also compiled using sama5_defconfig, all good.

The order in which they should be taken is 1/ a6e7f19c9100, then 2/ 3832b78b3ec2,
and 3/ e097eb7473d9.

Cheers,
ta

  reply	other threads:[~2021-01-05  8:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-20  8:28 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
2021-01-05  8:03       ` Tudor.Ambarus [this message]
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=b7747258-80dd-f5bd-6dd3-ea2cf410f86f@microchip.com \
    --to=tudor.ambarus@microchip.com \
    --cc=Ludovic.Desroches@microchip.com \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=gregkh@linuxfoundation.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

all inboxes | Powered by JetHome®