On Thu, 2013-07-11 at 17:05 +0800, Ming Lei wrote:

Hi,

As we are going to run URB->complete() in tasklet context[1][2],

Hi,

Please pardon my naivete, but why was it decided to use tasklets to defer work, as opposed to some other deferred work mechanism?

It seems to me that getting rid of tasklets has been an objective for years:

http://lwn.net/Articles/239633/ http://lwn.net/Articles/520076/ http://lwn.net/Articles/240054/

Regards, Andy

and hard interrupt may be enabled when running URB completion handler[3], so we might need to disable interrupt when acquiring one lock in the completion handler for the below reasons:

• URB->complete() holds a subsystem wide lock which may be acquired

in another hard irq context, and the subsystem wide lock is acquired by spin_lock()/read_lock()/write_lock() in complete()

• URB->complete() holds a private lock with spin_lock()/read_lock()/write_lock()

but driver may export APIs to make other drivers acquire the same private lock in its interrupt handler.

For the sake of safety and making the change simple, this patch set converts all spin_lock()/read_lock()/write_lock() in completion handler path into their irqsave version mechanically.

But if you are sure the above two cases do not happen in your driver, please let me know and I can drop the unnecessary change.

Also if you find some conversions are missed, also please let me know so that I can add it in the next round.

[1], http://marc.info/?l=linux-usb&m=137286322526312&w=2 [2], http://marc.info/?l=linux-usb&m=137286326726326&w=2 [3], http://marc.info/?l=linux-usb&m=137286330626363&w=2

[snip]

Thanks,

Ming Lei