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]

 



On Sat, 17 Mar 2012, Tejun Heo wrote:

> Hello, Alan.
> 
> On Sat, Mar 17, 2012 at 7:10 AM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote:
> >> Why not just lock out freezing across that issue / flush section?
> >
> > Currently there is no way to lock out freezing.
> 
> lock_system_sleep()?

That would work, _provided_ disk_clear_events() is never called in a 
freezable thread.  But if that never happens then the deadlock Oliver 
was worried about will never happen either.

> >�Besides, it may already have started.
> 
> What?

I don't know where disk_clear_events() gets called.  For example, is it
called by a user task when opening or closing a file or device?  If so
then it is freezable, which means that if a system sleep transition has
already started, the routine can't afford to wait until the sleep is
over.

Alan Stern

--
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