On Mon, 2012-06-04 at 11:12 +0200, Eric Dumazet wrote:
From: Eric Dumazet <edumazet@google.com>
drop_monitor calls several sleeping functions while in atomic context.
[<ffffffff816be6d0>] ? gs_change+0xb/0xb
Rework the logic to call the sleeping functions in right context.
Also avoid a loop if reset_per_cpu_data() cannot allocate memory :
use mod_timer() to wait 1/10 second before next try.
Signed-off-by: Eric Dumazet <edumazet@google.com>
Cc: Neil Horman <nhorman@tuxdriver.com>
---
I'll send a v2, please ignore this one