linux-kernel - Re: [1/3] scsi: lpfc: Fix memory leak in lpfc_config_port

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: <c8d2af7e-5ddf-4de2-ac1a-8a938280a0f4@web.de>
Date: Tue, 30 Dec 2025 08:28:37 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Zilin Guan <zilin@....edu.cn>, linux-scsi@...r.kernel.org
Cc: kernel-janitors@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
 James Bottomley <James.Bottomley@...senPartnership.com>,
 Jianhao Xu <jianhao.xu@....edu.cn>, Justin Tee <justin.tee@...adcom.com>,
 "Martin K. Petersen" <martin.petersen@...cle.com>,
 Paul Ely <paul.ely@...adcom.com>
Subject: Re: [1/3] scsi: lpfc: Fix memory leak in lpfc_config_port_post()

>> See also:
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.19-rc3#n262
…
> Regarding the stable kernel rules, do you consider this bug severe enough 
> to warrant a Cc: stable tag?

I suggest to take another look at information from previous discussions on
severity filters.

>                              Since this error path is unlikely to be 
> triggered during normal operation and the leak is small,

It seems that basic data processing was not hindered so far by the affected
function implementation.

>                                                          I didn't think 
> it was critical enough to bother the stable maintainers.

The tag “Fixes” is also an indication for related development considerations,
isn't it?

Regards,
Markus