lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <VI1PR07MB342111F8ED3EC0697F1B92D8A24F0@VI1PR07MB3421.eurprd07.prod.outlook.com>
Date:   Mon, 16 Oct 2017 04:35:11 +0000
From:   "Wang, Alan 1. (NSB - CN/Hangzhou)" <alan.1.wang@...ia-sbell.com>
To:     Frank Rowand <frowand.list@...il.com>,
        Rob Herring <robh+dt@...nel.org>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: RE: [PATCH] of: dynamic: fix memory leak related to properties of
 __of_node_dup

Hi Rob and Frank,

Thanks for your comments.
Frank's description is exactly what I meant. I will changed the description as yours if you don't mind.

We are using Linux v3.10.64 and a patch from https://lkml.org/lkml/2014/4/4/207.
With this patch all properties are added dynamically to the dynamic nodes. This is where I firstly found this issue using kmemleak.

And in our environment, the nodes for OCXO are kept empty in the dts file, and the properties will be generated at runtime 
according to sensor details read from ocxo EEPROM. In this case, I think memory leak remains on latest version when resetting that devices.

Thanks.
Lixin

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ