On Thu, Mar 17, 2011 at 09:13:08AM -0700, Greg KH wrote: > On Thu, Mar 17, 2011 at 10:53:33AM +0200, Michael S. Tsirkin wrote: > > irqfd in kvm used flush_work incorrectly: > > it assumed that work scheduled previously can't run > > after flush_work, but since kvm uses a non-reentrant > > workqueue (by means of schedule_work) > > we need flush_work_sync to get that guarantee. > > > > Signed-off-by: Michael S. Tsirkin <mst@xxxxxxxxxx> > > Reported-by: Jean-Philippe Menil <jean-philippe.menil@xxxxxxxxxxxxxx> > > Tested-by: Jean-Philippe Menil <jean-philippe.menil@xxxxxxxxxxxxxx> > > --- > > > > Note: this is needed for kernel 2.6.39 and earlier. > > This is not the correct way to submit patches for inclusion in the > stable kernel tree. Please read Documentation/stable_kernel_rules.txt > for how to do this properly. > > thanks, > > greg k-h What I missed is Cc: stable@xxxxxxxxxx in the text? OK, thanks for the correction. Actually I forgot, Avi and Marcelo want to handle stable patches for kvm themselves. Avi, Marcelo, right? So Greg, you can forget about this one for now. Thanks, -- MST -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
