Re: possible issue in: Block: use a freezable workqueue for disk-event polling (62d3c5439c534b0e6c653fc63e6d8c67be3a57b1)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am Freitag, 16. März 2012, 21:01:21 schrieb Rafael J. Wysocki:
> On Friday, March 16, 2012, Oliver Neukum wrote:
> > Am Freitag, 16. März 2012, 15:10:30 schrieb Alan Stern:
> > > > What happens if the freezer starts during the window? It seems to me
> > > > that the task flushing work would block and could not be frozen.
> > > 
> > > You're right.  I didn't check for flush_delayed_work() calls when 
> > > writing the patch.
> > > 
> > > I guess it would be okay if we first do cancel_delayed_work_sync() and
> > 
> > If you do that we would miss a change of medium. That is not really
> > acceptable.
> 
> Can you elaborate a bit, please?  What the exact scenario would be in that
> case?

When the freezer races sd_open() after a disk has been changed.

	Regards
		Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux