>>> Plus I'd >>>argue PF_MEMALLOC is a better solution anyway. >> >>It certainly seems like a more comprehensive fix for that >>particular class of problems! :) > > > Is it really more comprehensive? As I see it, it will only affect code > executed in the context of the usb-storage thread. But, what about code > which is invoked in tasklets or other contexts? Isn't it true that only that thread is allowed to submit usb-storage i/o requests? - Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: [linux-usb-devel] Re: USB hangsMatthew Dharm
- USB hangsAlan Cox
- Re: USB hangsMatthew Dharm
- Re: USB hangsAlan Cox
- Re: [linux-usb-devel] Re: USB hangsDavid Brownell
- Re: [linux-usb-devel] Re: USB hangsMatthew Dharm
- Prev by Date: Re: linux-2.4.24 released
- Next by Date: Re: Linux-2.6.1
- Previous by thread: Re: [linux-usb-devel] Re: USB hangs
- Next by thread: Re: [linux-usb-devel] Re: USB hangs
- Indexes:[Main][Thread]