Re: [PATCH v3] of: fix memory leak related to safe_name()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Wed, Jul 20, 2016 at 1:03 AM, Mathieu Malaterre
<mathieu.malaterre@xxxxxxxxx> wrote:
> On Fri, Jun 24, 2016 at 10:38 PM, Rob Herring <robh+dt@xxxxxxxxxx> wrote:
>> On Fri, Jun 17, 2016 at 2:51 AM, Mathieu Malaterre
>> <mathieu.malaterre@xxxxxxxxx> wrote:
>>> v3 tested here multiple times ! memleak is now gone.
>>>
>>> Tested-by: Mathieu Malaterre <mathieu.malaterre@xxxxxxxxx>
>>>
>>> Thanks
>>>
>>> On Thu, Jun 16, 2016 at 7:51 PM, Frank Rowand <frowand.list@xxxxxxxxx> wrote:
>>>> From: Frank Rowand <frank.rowand@xxxxxxxxxxx>
>>>>
>>>> Fix a memory leak resulting from memory allocation in safe_name().
>>>> This patch fixes all call sites of safe_name().
>>
>> Applied, thanks.
>>
>> Rob
>
> Could this patch be considered for stable ?

Yes, I tagged it for stable. I didn't send it for 4.7, so it won't go
in until after 4.8-rc1 though.

Rob
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]
  Powered by Linux