mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Yongzhi Liu <hyperlyzcs@gmail.com>,
	GR-QLogic-Storage-Upstream@marvell.com,
	linux-scsi@vger.kernel.org, kernel-janitors@vger.kernel.org,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Nilesh Javali <njavali@marvell.com>,
	Saurav Kashyap <skashyap@marvell.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Himanshu Madhani <himanshu.madhani@oracle.com>,
	huntazhang@tencent.com, jitxie@tencent.com
Subject: Re: [PATCH V3 1/2] scsi: qla2xxx: Fix double free of fcport in qla24xx_els_dcmd_iocb
Date: Tue, 30 Apr 2024 11:55:31 +0200	[thread overview]
Message-ID: <54e83ce6-0f9d-45c2-92c7-a41fdb812314@web.de> (raw)
In-Reply-To: <20240430091144.10744-1-hyperlyzcs@gmail.com>

* I would usually expect a corresponding cover letter for patch series.

* Would you like to add parentheses to the function name in the summary phrase?


> When dma_alloc_coherent() or qla2x00_start_sp() return an error,

                                                  call returned?


> the callback function qla2x00_els_dcmd_sp_free in qla2x00_sp_release
> will call qla2x00_free_fcport() to kfree fcport. We shouldn't call

                                     free “fcport”?


> qla2x00_free_fcport() again in the error handling path.

                                                    paths?



> Fix this by cleaning the duplicate qla2x00_free_fcport() calls up.

Would the wording “Thus delete duplicate qla2x00_free_fcport() calls.” be a bit nicer?


…
> ---
> V2 -> V3: Improve patch summary and provide a patch serises with two separate update steps
…

* How do you think about to avoid the repetition of version identifiers
  (according to the selected enumeration style)?

* You would probably like to avoid another typo here.

Regards,
Markus

      parent reply	other threads:[~2024-04-30  9:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25  9:37 [PATCH] scsi: qla2xxx: Fix double free of fcport in error handling path Yongzhi Liu
2024-04-25 11:31 ` Markus Elfring
2024-04-28 11:34   ` [PATCH V2] " Yongzhi Liu
2024-04-28 12:52     ` Markus Elfring
2024-04-29  5:12     ` Markus Elfring
2024-04-30  9:11       ` [PATCH V3 1/2] scsi: qla2xxx: Fix double free of fcport in qla24xx_els_dcmd_iocb Yongzhi Liu
2024-04-30  9:11         ` [PATCH V3 2/2] scsi: qla2xxx: Optimisation of exception handling " Yongzhi Liu
2024-04-30 11:21           ` Markus Elfring
2024-05-06 12:38             ` [PATCH V4 0/2] Bugfix and optimisation of exception handling Yongzhi Liu
2024-05-06 12:38               ` [PATCH V4 1/2] scsi: qla2xxx: Fix double free of fcport in qla24xx_els_dcmd_iocb() Yongzhi Liu
2024-05-06 12:38               ` [PATCH V4 2/2] scsi: qla2xxx: Use common error handling code " Yongzhi Liu
2024-04-30  9:55         ` Markus Elfring [this message]

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=54e83ce6-0f9d-45c2-92c7-a41fdb812314@web.de \
    --to=markus.elfring@web.de \
    --cc=GR-QLogic-Storage-Upstream@marvell.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=himanshu.madhani@oracle.com \
    --cc=huntazhang@tencent.com \
    --cc=hyperlyzcs@gmail.com \
    --cc=jitxie@tencent.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=njavali@marvell.com \
    --cc=skashyap@marvell.com \
    /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

all inboxes | Powered by JetHome®