Re: [patch 1/9] x86, ioapic: fix potential resume deadlock
From: Chuck Ebbert
Date: Fri May 20 2011 - 00:14:00 EST
On Wed, 18 May 2011 16:31:31 -0700
Suresh Siddha <suresh.b.siddha@xxxxxxxxx> wrote:
> From: Daniel J Blueman <daniel.blueman@xxxxxxxxx>
> Fix a potential deadlock when resuming; here the calling function
> has disabled interrupts, so we cannot sleep.
> Change the memory allocation flag from GFP_KERNEL to GFP_ATOMIC.
> TODO: We can do away with this memory allocation during resume by
> reusing the ioapic suspend/resume code that uses boot time allocated
> Signed-off-by: Daniel J Blueman <daniel.blueman@xxxxxxxxx>
> Signed-off-by: Suresh Siddha <suresh.b.siddha@xxxxxxxxx>
> Cc: <stable@xxxxxxxxxx> # v2.6.39
This is happening on 2.6.38 as well.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/