Re: [PATCH 5/5] usb_debug: EXPERIMENTAL - poll hcd device to forcewrites

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

 



Greg KH wrote:
>> Doing enough printk's such as in register_console() will cause loss
>> because you run out of URBs unless you can force them to complete.
>>     
>
> Why not just make the upper bound of urbs very large?  We used to have
> an unlimited number of in-flight urbs for some drivers until it was
> pointed out that a simple:
> 	cat /dev/null > /dev/ttyUSB0
> would cause a DoS :)
>
> What happens if your upper bound is 400?  4000?  Will that work
> properly?
>   
Sure, if you have enough of a urb available, ultimately you get all the
printk's.

If I want to printk from the nmi_watchdog out to this device, am I going
to get anything if the write is not synchronous, because in theory the
hcd device is never going to get accessed again?

Ideally I want to make sure that somehow I get my debug output out to
the console, even if it means we do some polling after the oops state is
set.

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