From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Long Li <longli@microsoft.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Haiyang Zhang <haiyangz@microsoft.com>,
"James E . J . Bottomley" <JBottomley@odin.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>
Subject: Re: [PATCH] storvsc: fix memory leak on ring buffer busy
Date: Wed, 30 Aug 2017 21:55:10 -0400 [thread overview]
Message-ID: <yq1y3q0y001.fsf@oracle.com> (raw)
In-Reply-To: <MWHPR21MB0190F8C50CCF7CFA0EDCA7A6CE9C0@MWHPR21MB0190.namprd21.prod.outlook.com> (Long Li's message of "Wed, 30 Aug 2017 03:48:54 +0000")
Long,
>> Which kernel version is this patch aimed at?
>
> Martin, thanks for pointing this out. This should also go to stable
> trees.
The reason I asked is that it didn't apply to neither fixes, nor
for-next.
I applied it to 4.13/scsi-fixes by hand and added a stable tag.
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Long Li <longli@microsoft.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
KY Srinivasan <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
"James E . J . Bottomley" <JBottomley@odin.com>,
"devel\@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"linux-scsi\@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] storvsc: fix memory leak on ring buffer busy
Date: Wed, 30 Aug 2017 21:55:10 -0400 [thread overview]
Message-ID: <yq1y3q0y001.fsf@oracle.com> (raw)
In-Reply-To: <MWHPR21MB0190F8C50CCF7CFA0EDCA7A6CE9C0@MWHPR21MB0190.namprd21.prod.outlook.com> (Long Li's message of "Wed, 30 Aug 2017 03:48:54 +0000")
Long,
>> Which kernel version is this patch aimed at?
>
> Martin, thanks for pointing this out. This should also go to stable
> trees.
The reason I asked is that it didn't apply to neither fixes, nor
for-next.
I applied it to 4.13/scsi-fixes by hand and added a stable tag.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-08-31 1:55 UTC|newest]
Thread overview: 10+ 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 1:31 ` Martin K. Petersen
2017-08-30 3:48 ` Long Li
2017-08-30 3:48 ` Long Li
2017-08-31 1:55 ` Martin K. Petersen [this message]
2017-08-31 1:55 ` Martin K. Petersen
2017-08-31 2:28 ` Long Li
2017-08-31 2:28 ` Long Li
2017-08-30 15:11 ` Stephen Hemminger
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=yq1y3q0y001.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--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@microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.