From: Markus Elfring <Markus.Elfring@web.de>
To: Zilin Guan <zilin@seu.edu.cn>, linux-scsi@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Jianhao Xu <jianhao.xu@seu.edu.cn>,
Justin Tee <justin.tee@broadcom.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Paul Ely <paul.ely@broadcom.com>
Subject: Re: [1/3] scsi: lpfc: Fix memory leak in lpfc_config_port_post()
Date: Tue, 30 Dec 2025 08:28:37 +0100 [thread overview]
Message-ID: <c8d2af7e-5ddf-4de2-ac1a-8a938280a0f4@web.de> (raw)
In-Reply-To: <20251230062008.1021449-1-zilin@seu.edu.cn>
>> 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
next prev parent reply other threads:[~2025-12-30 7:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251229071515.155412-2-zilin@seu.edu.cn>
2025-12-29 9:09 ` [PATCH 1/3] scsi: lpfc: Fix memory leak in lpfc_config_port_post() Markus Elfring
2025-12-30 6:20 ` Zilin Guan
2025-12-30 7:28 ` Markus Elfring [this message]
2025-12-30 9:05 ` [1/3] " Zilin Guan
2026-01-05 9:53 ` [PATCH 1/3] " Dan Carpenter
2026-01-05 10:17 ` Dan Carpenter
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=c8d2af7e-5ddf-4de2-ac1a-8a938280a0f4@web.de \
--to=markus.elfring@web.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jianhao.xu@seu.edu.cn \
--cc=justin.tee@broadcom.com \
--cc=kernel-janitors@vger.kernel.org \
--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