linux-kernel - Re: [PATCH 0/3] Use scope based cleanup in drivers/soc/ti/

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: <Zj81C3OZjxB4vtrW@five231003>
Date: Sat, 11 May 2024 14:36:19 +0530
From: Kousik Sanagavarapu <five231003@...il.com>
To: Nishanth Menon <nm@...com>, Santosh Shilimkar <ssantosh@...nel.org>,
	Julia Lawall <julia.lawall@...ia.fr>
Cc: Shuah Khan <skhan@...uxfoundation.org>,
	Javier Carrasco <javier.carrasco.cruz@...il.com>,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/3] Use scope based cleanup in drivers/soc/ti/

On Fri, May 10, 2024 at 08:17:54AM -0500, Nishanth Menon wrote:
> On 12:38-20240510, Kousik Sanagavarapu wrote:
> > Do scope based "struct device_node" cleanup in drivers/soc/ti/*.  This
> > series converts all the possible cases.
> 
> Thank you - also will be great if you can indicate how this was caught?

This is kind of a refactoring.  I grepped for them manually.

As for the motivation itself, I would say

	https://lwn.net/Articles/934679/

Me and the other LKMP mentees are working on doing this to various parts
of the source with the help of Julia, Shuah and Javier.

As mentioned in the commit messages, this refactoring has the advantage
of reducing the number of leaks in case we add new code in the future
introducing new OF stuff.

Thanks

PS: I sent out the cover letter once before without CCing the mailing
lists and Nishanth replied to that.  So that mail can't be seen here
independently.