> -----Original Message----- > From: Greg KH [mailto:gregkh@xxxxxxxxxxxxxxxxxxx] > Sent: Monday, August 26, 2013 4:14 PM > To: KY Srinivasan > Cc: linux-kernel@xxxxxxxxxxxxxxx; devel@xxxxxxxxxxxxxxxxxxxxxx; olaf@xxxxxxxxx; > apw@xxxxxxxxxxxxx; jasowang@xxxxxxxxxx; stable@xxxxxxxxxxxxxxx > Subject: Re: [PATCH 1/1] Drivers: hv: vmbus: Fix a bug in the handling of channel > offers > > On Mon, Aug 26, 2013 at 10:48:16PM +0000, KY Srinivasan wrote: > > > > > > > -----Original Message----- > > > From: Greg KH [mailto:gregkh@xxxxxxxxxxxxxxxxxxx] > > > Sent: Monday, August 26, 2013 2:57 PM > > > To: KY Srinivasan > > > Cc: linux-kernel@xxxxxxxxxxxxxxx; devel@xxxxxxxxxxxxxxxxxxxxxx; > olaf@xxxxxxxxx; > > > apw@xxxxxxxxxxxxx; jasowang@xxxxxxxxxx; stable@xxxxxxxxxxxxxxx > > > Subject: Re: [PATCH 1/1] Drivers: hv: vmbus: Fix a bug in the handling of > channel > > > offers > > > > > > On Mon, Aug 26, 2013 at 02:08:58PM -0700, K. Y. Srinivasan wrote: > > > > The channel state should be correctly set before registering the device. In > the > > > current > > > > code the driver probe would fail for channels that have been rescinded and > > > subsequently > > > > re-offered. Fix the bug. > > > > > > > > Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx> > > > > Cc: <stable@xxxxxxxxxxxxxxx> > > > > > > What older kernel versions have this bug? When did it show up? > > > > The patch that introduced the bug is: > > > > commit e68d2971d26577b932a16333ce165af98a96e068 > > Author: K. Y. Srinivasan <kys@xxxxxxxxxxxxx> > > Date: Thu May 23 12:02:32 2013 -0700 > > > > Drivers: hv: vmbus: Implement multi-channel support > > > > I think 3.10 shipped with this bug. > > Why do you think that, it's not what git shows: > $ git describe --contains e68d2971d26577b932a16333ce165af98a96e068 > v3.11-rc1~157^2~64 > > So this is a 3.11-only thing, right? My mistake; I was looking at some version of linux-3.10 code that had this problem and so I assumed it must have shipped in 3.10. Regards, K. Y > > thanks, > > greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel