From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: John Garry <john.garry@huawei.com>
Cc: <jejb@linux.vnet.ibm.com>, <martin.petersen@oracle.com>,
<hch@lst.de>, <linux-scsi@vger.kernel.org>,
<chenxiang66@hisilicon.com>, <linux-kernel@vger.kernel.org>,
<yanaijie@huawei.com>
Subject: Re: [PATCH] scsi: scsi_transport_sas: Fix memory leak when removing devices
Date: Thu, 21 Nov 2019 21:13:12 -0500 [thread overview]
Message-ID: <yq136egd5fr.fsf@oracle.com> (raw)
In-Reply-To: <1574242755-94156-1-git-send-email-john.garry@huawei.com> (John Garry's message of "Wed, 20 Nov 2019 17:39:15 +0800")
John,
> Removing a non-host rphy causes a memory leak:
Applied to 5.5/scsi-queue, thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2019-11-22 2:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 9:39 [PATCH] scsi: scsi_transport_sas: Fix memory leak when removing devices John Garry
2019-11-22 2:13 ` Martin K. Petersen [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=yq136egd5fr.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=chenxiang66@hisilicon.com \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=yanaijie@huawei.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