Linux SCSI subsystem development
 help / color / mirror / Atom feed
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 16:54:39 +0100	[thread overview]
Message-ID: <3d1aa2f6-37fb-48f3-936e-95c779a8e7ff@web.de> (raw)
In-Reply-To: <20260103152514.304387-1-zilin@seu.edu.cn>

>> 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?
…
> We are aware of these ethics requirements and strictly respect them.
> For example, we responsibly disclose our findings (i.e., bugs, in the 
> form of patches),

Thanks for your contributions.


>                   and we will make our paper and code public after 
> publication. However, we cannot disclose our tool at this moment because 
> our research is still ongoing.

Do the researcher guidelines indicate a need to point research activities out
in more explicit ways?

Does your email address indicate a relationship with the Southeast University?
Is the School of Information Science and Engineering involved here?

Regards,
Markus

  reply	other threads:[~2026-01-03 15:54 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
2026-01-03 15:25       ` Zilin Guan
2026-01-03 15:54         ` Markus Elfring [this message]
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=3d1aa2f6-37fb-48f3-936e-95c779a8e7ff@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