[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8AFC7968D54FB448A30D8F38F259C56223FE8B19@TK5EX14MBXC114.redmond.corp.microsoft.com>
Date: Wed, 4 Aug 2010 04:35:06 +0000
From: Hank Janssen <hjanssen@...rosoft.com>
To: Greg KH <gregkh@...e.de>
CC: "'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>,
"'devel@...verdev.osuosl.org'" <devel@...verdev.osuosl.org>,
"'virtualization@...ts.osdl.org'" <virtualization@...ts.osdl.org>,
"Haiyang Zhang" <haiyangz@...rosoft.com>
Subject: RE: [PATCH 1/6] staging: hv: Fixed bounce kmap problem by using
correct index
And then Greg spoke:
>>On Tue, Aug 03, 2010 at 05:31:51PM +0000, Hank Janssen wrote:
>> From: Hank Janssen <hjanssen@...rosoft.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.
Hank.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists