Greg KH <[email protected]> writes: > On Wed, Feb 06, 2013 at 10:38:36AM +1030, Rusty Russell wrote: >> Amit Shah <[email protected]> writes: >> > On (Mon) 04 Feb 2013 [10:09:05], Rusty Russell wrote: >> >> Amit Shah <[email protected]> writes: >> >> > On (Thu) 17 Jan 2013 [13:21:32], [email protected] wrote: >> >> >> From: Sjur Brændeland <[email protected]> >> >> >> >> >> >> Don't access uninitialized work-queue when removing device. >> >> >> The work queue is initialized only if the device multi-queue. >> >> >> So don't call cancel_work unless this is a multi-queue device. >> >> >> >> >> >> This fixes the following panic: >> >> > >> >> > [snip] >> >> > >> >> >> Signed-off-by: Sjur Brændeland <[email protected]> >> >> > >> >> > Acked-by: Amit Shah <[email protected]> >> >> > >> >> >> This fix is intended of v3.8. >> >> > >> >> > Should also be CC'ed to stable@ >> ... >> >> I've already sent it to Linus. Sjur said: "This fix is intended of >> >> v3.8.". If it needs to be in -stable, please tell me and I'll fwd it >> >> manually. >> > >> > This can result in a panic when removing the device or module (when >> > not using multiport). I'd vote for submitting to stable. >> > >> > Amit >> >> OK stable, please cherry-pick from Linus' tree: >> >> commit b26ada9abe26290b1dcd06075935b977548c50db >> Author: Sjur Brændeland <[email protected]> >> Date: Tue Jan 22 09:50:26 2013 +1030 >> >> virtio_console: Don't access uninitialized data. > > $ git show b26ada9abe26290b1dcd06075935b977548c50db > fatal: bad object b26ada9abe26290b1dcd06075935b977548c50db > > What am I missing here?
My mistake, Linus has not pulled this. I have added CC:stable, and will request now. Sorry for the noise, Rusty. -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
