linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Long Li <longli@exchange.microsoft.com>,
	linux-scsi@vger.kernel.org,
	Haiyang Zhang <haiyangz@microsoft.com>,
	"James E . J . Bottomley" <JBottomley@odin.com>,
	linux-kernel@vger.kernel.org, devel@linuxdriverproject.org
Subject: Re: [PATCH] storvsc: fix memory leak on ring buffer busy
Date: Wed, 30 Aug 2017 08:11:01 -0700	[thread overview]
Message-ID: <20170830081101.5307095d@xeon-e3> (raw)
In-Reply-To: <yq18ti1265c.fsf@oracle.com>

On Tue, 29 Aug 2017 21:31:11 -0400
"Martin K. Petersen" <martin.petersen@oracle.com> wrote:

> Long,
> 
> > When storvsc is sending I/O to Hyper-v, it may allocate a bigger
> > buffer descriptor for large data payload that can't fit into a
> > pre-allocated buffer descriptor. This bigger buffer is freed on return
> > path.
> >
> > If I/O request to Hyper-v fails due to ring buffer busy, the storvsc
> > allocated buffer descriptor should also be freed.  
> 
> Which kernel version is this patch aimed at?
> 

Looks like this an old issue. Probably should add

Fixes: be0cf6ca301c ("scsi: storvsc: Set the tablesize based on the information given by the host")

      parent reply	other threads:[~2017-08-30 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29  0:43 [PATCH] storvsc: fix memory leak on ring buffer busy Long Li
2017-08-30  1:31 ` Martin K. Petersen
2017-08-30  3:48   ` Long Li
2017-08-31  1:55     ` Martin K. Petersen
2017-08-31  2:28       ` Long Li
2017-08-30 15:11   ` Stephen Hemminger [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=20170830081101.5307095d@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=JBottomley@odin.com \
    --cc=devel@linuxdriverproject.org \
    --cc=haiyangz@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=longli@exchange.microsoft.com \
    --cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).