From: Markus Elfring <Markus.Elfring@web.de>
To: Jianhao Xu <jianhao.xu@seu.edu.cn>, Zilin Guan <zilin@seu.edu.cn>,
linux-scsi@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Justin Tee <justin.tee@broadcom.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Paul Ely <paul.ely@broadcom.com>
Subject: Re: [v3 0/3] scsi: lpfc: Fix multiple memory leaks in error paths
Date: Sat, 3 Jan 2026 14:30:36 +0100 [thread overview]
Message-ID: <411ef9b1-ff0c-4f68-8af8-f3a478ca0d7d@web.de> (raw)
In-Reply-To: <20260103125418.179210-1-zilin@seu.edu.cn>
>> …
>>> 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
next prev parent reply other threads:[~2026-01-03 13:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 15:11 [PATCH v3 0/3] scsi: lpfc: Fix multiple memory leaks in error paths Zilin Guan
2025-12-31 15:11 ` [PATCH v3 1/3] scsi: lpfc: Fix memory leak in lpfc_config_port_post() Zilin Guan
2025-12-31 15:11 ` [PATCH v3 2/3] scsi: lpfc: Fix memory leak in lpfc_sli4_driver_resource_setup() Zilin Guan
2025-12-31 15:11 ` [PATCH v3 3/3] scsi: lpfc: Fix memory leak in lpfc_cmpl_plogi_plogi_issue() Zilin Guan
2025-12-31 16:33 ` [v3 0/3] scsi: lpfc: Fix multiple memory leaks in error paths Markus Elfring
2026-01-03 12:54 ` Zilin Guan
2026-01-03 13:30 ` Markus Elfring [this message]
2026-01-03 15:25 ` Zilin Guan
2026-01-03 15:54 ` Markus Elfring
2026-01-04 4:37 ` Zilin Guan
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=411ef9b1-ff0c-4f68-8af8-f3a478ca0d7d@web.de \
--to=markus.elfring@web.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jianhao.xu@seu.edu.cn \
--cc=justin.tee@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=paul.ely@broadcom.com \
--cc=zilin@seu.edu.cn \
/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