All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Hank Janssen <hjanssen@microsoft.com>
Cc: "'devel@driverdev.osuosl.org'" <devel@driverdev.osuosl.org>,
	"'virtualization@lists.osdl.org'" <virtualization@lists.osdl.org>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/6] staging: hv: Fixed bounce kmap problem by using correct index
Date: Wed, 4 Aug 2010 10:04:06 -0700	[thread overview]
Message-ID: <20100804170406.GA28217@suse.de> (raw)
In-Reply-To: <8AFC7968D54FB448A30D8F38F259C56223FE8B19@TK5EX14MBXC114.redmond.corp.microsoft.com>

On Wed, Aug 04, 2010 at 04:35:06AM +0000, Hank Janssen wrote:
> 
> And then Greg spoke:
> >>On Tue, Aug 03, 2010 at 05:31:51PM +0000, Hank Janssen wrote:
> >> From: Hank Janssen <hjanssen@microsoft.com>
> >> 
> > >Fixed bounce offset kmap problem by using correct index
> >
> >Is this a bugfix that needs to go to previous kernel releases?  If so, which ones?  What is the symptom of the problem here?
> 
> Yes, this should be backported to all stable kernel releases that have the Hyper-V drivers In them.  
> 
> The symptom of the problem is that in some NAS appliances this problem represents
> Itself by a unresponsive VM under a load with many clients writing small files.
> 
> I actually goofed up in my previous code and used an incorrect index number
> For this part of the code. It should have shown up in more situations than what
> I have seen oddly enough.

Please provide this type of information in the changelog section.

If you want something backported to older stable kernels, add a:
	Cc: stable <stable@kernel.org>
to the signed-off-by area of the patch and it will be automatically sent
to the stable alias when it gets included in Linus's tree so I know to
pick it up then.

Care to resend all of these patches based on these comments?

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@suse.de>
To: Hank Janssen <hjanssen@microsoft.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"'devel@driverdev.osuosl.org'" <devel@driverdev.osuosl.org>,
	"'virtualization@lists.osdl.org'" <virtualization@lists.osdl.org>,
	Haiyang Zhang <haiyangz@microsoft.com>
Subject: Re: [PATCH 1/6] staging: hv: Fixed bounce kmap problem by using correct index
Date: Wed, 4 Aug 2010 10:04:06 -0700	[thread overview]
Message-ID: <20100804170406.GA28217@suse.de> (raw)
In-Reply-To: <8AFC7968D54FB448A30D8F38F259C56223FE8B19@TK5EX14MBXC114.redmond.corp.microsoft.com>

On Wed, Aug 04, 2010 at 04:35:06AM +0000, Hank Janssen wrote:
> 
> And then Greg spoke:
> >>On Tue, Aug 03, 2010 at 05:31:51PM +0000, Hank Janssen wrote:
> >> From: Hank Janssen <hjanssen@microsoft.com>
> >> 
> > >Fixed bounce offset kmap problem by using correct index
> >
> >Is this a bugfix that needs to go to previous kernel releases?  If so, which ones?  What is the symptom of the problem here?
> 
> Yes, this should be backported to all stable kernel releases that have the Hyper-V drivers In them.  
> 
> The symptom of the problem is that in some NAS appliances this problem represents
> Itself by a unresponsive VM under a load with many clients writing small files.
> 
> I actually goofed up in my previous code and used an incorrect index number
> For this part of the code. It should have shown up in more situations than what
> I have seen oddly enough.

Please provide this type of information in the changelog section.

If you want something backported to older stable kernels, add a:
	Cc: stable <stable@kernel.org>
to the signed-off-by area of the patch and it will be automatically sent
to the stable alias when it gets included in Linus's tree so I know to
pick it up then.

Care to resend all of these patches based on these comments?

thanks,

greg k-h

  reply	other threads:[~2010-08-04 17:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03 17:31 [PATCH 1/6] staging: hv: Fixed bounce kmap problem by using correct index Hank Janssen
2010-08-03 17:31 ` Hank Janssen
2010-08-03 17:37 ` Greg KH
2010-08-03 17:37   ` Greg KH
2010-08-04  4:35   ` Hank Janssen
2010-08-04 17:04     ` Greg KH [this message]
2010-08-04 17:04       ` Greg KH
2010-08-04 17:17       ` Hank Janssen
2010-08-04 18:23         ` Greg KH
2010-08-04 18:23           ` Greg KH
2010-08-04 18:50           ` Hank Janssen
2010-08-04 19:28             ` Greg KH

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=20100804170406.GA28217@suse.de \
    --to=gregkh@suse.de \
    --cc=devel@driverdev.osuosl.org \
    --cc=haiyangz@microsoft.com \
    --cc=hjanssen@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.osdl.org \
    /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.