This is a note to let you know that I've just added the patch titled
spi/pxa2xx: use GFP_ATOMIC in sg table allocation
to the 3.9-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
spi-pxa2xx-use-gfp_atomic-in-sg-table-allocation.patch
and it can be found in the queue-3.9 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From 5548f98c46538d1da04eff179a52e50537d11465 Mon Sep 17 00:00:00 2001
From: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx>
Date: Tue, 18 Jun 2013 17:29:44 +0300
Subject: spi/pxa2xx: use GFP_ATOMIC in sg table allocation
From: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx>
commit 5548f98c46538d1da04eff179a52e50537d11465 upstream.
pxa2xx_spi_map_dma_buffer() gets called in tasklet context so we can't
sleep when we allocate a new sg table. Use GFP_ATOMIC here instead.
Signed-off-by: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx>
Signed-off-by: Mark Brown <broonie@xxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/spi/spi-pxa2xx-dma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/spi/spi-pxa2xx-dma.c
+++ b/drivers/spi/spi-pxa2xx-dma.c
@@ -59,7 +59,7 @@ static int pxa2xx_spi_map_dma_buffer(str
int ret;
sg_free_table(sgt);
- ret = sg_alloc_table(sgt, nents, GFP_KERNEL);
+ ret = sg_alloc_table(sgt, nents, GFP_ATOMIC);
if (ret)
return ret;
}
Patches currently in stable-queue which might be from mika.westerberg@xxxxxxxxxxxxxxx are
queue-3.9/spi-pxa2xx-use-gfp_atomic-in-sg-table-allocation.patch
queue-3.9/acpi-resources-call-acpi_get_override_irq-only-for-legacy-irq-resources.patch
queue-3.9/spi-pxa2xx-fix-memory-corruption-due-to-wrong-size-used-in-devm_kzalloc.patch
queue-3.9/acpi-pm-fix-error-code-path-for-power-resources.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html