From: Greg KH <greg@kroah.com>
To: tang.junhui@zte.com.cn
Cc: bart.vanassche@sandisk.com, stable@vger.kernel.org,
zhang.kai16@zte.com.cn
Subject: Re: [PATCH] scsi_dh_alua: fix meory leak in alua_rtpg()
Date: Fri, 30 Sep 2016 06:54:17 +0200 [thread overview]
Message-ID: <20160930045417.GA4625@kroah.com> (raw)
In-Reply-To: <1475199347-7276-1-git-send-email-tang.junhui@zte.com.cn>
On Fri, Sep 30, 2016 at 09:35:47AM +0800, tang.junhui@zte.com.cn wrote:
> From: "tang.junhui" <tang.junhui@zte.com.cn>
>
> buff should be freed before returning with SCSI_DH_RETRY in alua_rtpg().
>
> Signed-off-by: tang.junhui <tang.junhui@zte.com.cn>
> ---
> drivers/scsi/device_handler/scsi_dh_alua.c | 1 +
> 1 file changed, 1 insertion(+)
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read Documentation/stable_kernel_rules.txt
for how to do this properly.
</formletter>
prev parent reply other threads:[~2016-09-30 5:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 1:35 [PATCH] scsi_dh_alua: fix meory leak in alua_rtpg() tang.junhui
2016-09-30 4:54 ` Greg KH [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=20160930045417.GA4625@kroah.com \
--to=greg@kroah.com \
--cc=bart.vanassche@sandisk.com \
--cc=stable@vger.kernel.org \
--cc=tang.junhui@zte.com.cn \
--cc=zhang.kai16@zte.com.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;
as well as URLs for NNTP newsgroup(s).