staging: hv: Fixed the value of the 64bit-hole inside ring buffer
in [Kernel]
|
Prev: staging: hv: Increased storvsc ringbuffer and max_io_requests
Next: staging: hv: Gracefully handle SCSI resets
From: Greg KH on 3 Aug 2010 13:50 On Tue, Aug 03, 2010 at 05:31:57PM +0000, Hank Janssen wrote: > From: Haiyang Zhang <haiyangz(a)microsoft.com> > > Fixed the value of the 64bit-hole inside ring buffer, this caused a problem on Hyper-V when running checked Windows builds. What was the problem, and why would this fix it? Was it a bug in this code, by virtue that the code was incorrect in the client and the checked builds properly warned of this, or something else? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Hank Janssen on 4 Aug 2010 00:30 >>On Tue, Aug 03, 2010 at 05:31:57PM +0000, Hank Janssen wrote: >> From: Haiyang Zhang <haiyangz(a)microsoft.com> >> >> Fixed the value of the 64bit-hole inside ring buffer, this caused a problem on Hyper-V >>when running checked Windows builds. > >What was the problem, and why would this fix it? Was it a bug in this code, >by virtue that the code was incorrect in the client and the checked builds properly warned >of this, or something else? Checked builds of Windows are used internally and given to external system builders at times. They are builds that for example that all elements in a structure follow the definition of that Structure. The bug this fixed was for a field that we did not fill in at all (Because we do Not use it on the Linux side), and the checked build of windows gives errors on it internally to the Windows logs. This fixes that error. Thanks, Hank. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Greg KH on 4 Aug 2010 13:20
On Wed, Aug 04, 2010 at 04:25:40AM +0000, Hank Janssen wrote: > > >>On Tue, Aug 03, 2010 at 05:31:57PM +0000, Hank Janssen wrote: > >> From: Haiyang Zhang <haiyangz(a)microsoft.com> > >> > >> Fixed the value of the 64bit-hole inside ring buffer, this caused a problem on Hyper-V > >>when running checked Windows builds. > > > >What was the problem, and why would this fix it? Was it a bug in this code, > >by virtue that the code was incorrect in the client and the checked builds properly warned > >of this, or something else? > > Checked builds of Windows are used internally and given to external system builders at times. > They are builds that for example that all elements in a structure follow the definition of that > Structure. The bug this fixed was for a field that we did not fill in at all (Because we do > Not use it on the Linux side), and the checked build of windows gives errors on it internally > to the Windows logs. > > This fixes that error. Wonderful, please provide this information in the changelog comment. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |