[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <411ef9b1-ff0c-4f68-8af8-f3a478ca0d7d@web.de>
Date: Sat, 3 Jan 2026 14:30:36 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Jianhao Xu <jianhao.xu@....edu.cn>, Zilin Guan <zilin@....edu.cn>,
linux-scsi@...r.kernel.org
Cc: LKML <linux-kernel@...r.kernel.org>,
James Bottomley <James.Bottomley@...senPartnership.com>,
Justin Tee <justin.tee@...adcom.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Paul Ely <paul.ely@...adcom.com>
Subject: Re: [v3 0/3] scsi: lpfc: Fix multiple memory leaks in error paths
>> …
>>> These issues were identified during static analysis.
>>
>> How do you think about to share further information according to
>> your source code analysis approach?
…
> Thank you for your inquiry.
>
> I believe the commit messages in each individual patch within this series
> already provide a clear and specific description of the identified issues
> and the analysis of the failure paths.
You presented interesting development ideas.
Will any related concerns become relevant here?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/researcher-guidelines.rst?h=v6.19-rc3#n5
Did your analysis approach get a corresponding name?
Regards,
Markus
Powered by blists - more mailing lists