[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110520000903.2d8d05a4@katamari>
Date: Fri, 20 May 2011 00:09:03 -0400
From: Chuck Ebbert <cebbert@...hat.com>
To: Suresh Siddha <suresh.b.siddha@...el.com>
Cc: mingo@...e.hu, tglx@...utronix.de, hpa@...or.com,
linux-kernel@...r.kernel.org, daniel.blueman@...il.com,
suresh.b.siddha@...el.com, <stable@...nel.org>
Subject: Re: [patch 1/9] x86, ioapic: fix potential resume deadlock
On Wed, 18 May 2011 16:31:31 -0700
Suresh Siddha <suresh.b.siddha@...el.com> wrote:
> From: Daniel J Blueman <daniel.blueman@...il.com>
>
> 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
> buffers.
>
> Signed-off-by: Daniel J Blueman <daniel.blueman@...il.com>
> Signed-off-by: Suresh Siddha <suresh.b.siddha@...el.com>
> Cc: <stable@...nel.org> # 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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists