linux-kernel - Re: [v3 0/3] scsi: lpfc: Fix multiple memory leaks in error paths

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] [day] [month] [year] [list]

Message-Id: <20260104043739.50700-1-zilin@seu.edu.cn>
Date: Sun,  4 Jan 2026 04:37:39 +0000
From: Zilin Guan <zilin@....edu.cn>
To: markus.elfring@....de
Cc: James.Bottomley@...senPartnership.com,
	jianhao.xu@....edu.cn,
	justin.tee@...adcom.com,
	linux-kernel@...r.kernel.org,
	linux-scsi@...r.kernel.org,
	martin.petersen@...cle.com,
	paul.ely@...adcom.com,
	zilin@....edu.cn
Subject: Re: [v3 0/3] scsi: lpfc: Fix multiple memory leaks in error paths

On Sat, Jan 03, 2026 at 04:54:39PM +0100, Markus Elfring wrote:
> Do the researcher guidelines indicate a need to point research activities out
> in more explicit ways?

No, as our research does not constitute "active research on developer 
behavior", but rather consists of "good faith contributions". It is 
governed by and conducted in full compliance with both the Linux Kernel's 
Researcher Guidelines and the relevant security conference guidelines for 
vulnerability disclosure (e.g., IEEE S&P: https://sp2026.ieee-security.org/cfpapers.html).

I appreciate your engagement, but we must stay on point. Your frequent 
questions unrelated to the technical content of many my patches are 
causing distractions and creating noise in the discussion. Therefore, 
I will no longer respond to off-topic inquiries in this public channel.

Regards,
Zilin Guan