On 01/29/2013 12:21 PM, Eric Dumazet wrote:

On Tue, 2013-01-29 at 12:00 -0800, Ben Greear wrote:

quoted

I think there was a proposal to change it to schedule_timeout_uninterruptible(1);
some time ago, but that change never made it upstream (at least not in 3.7.5)?

Thanks,
Ben

Honestly we should fix the bug at this point, not hide it.

We could use msleep(2500) to make sure people will complain ;)

Well, few will notice that either, or at least are unlikely
to know what to blame.

If we should just never reach that code, maybe a WARN_ON_ONCE() when
we do?

Thanks,
Ben


-- 
Ben Greear [off-list ref]
Candela Technologies Inc  http://www.candelatech.com