[MTD] [OneNAND] omap2: panic_write may be in an interrupt context
authorAdrian Hunter <adrian.hunter@nokia.com>
Mon, 23 Mar 2009 12:57:38 +0000 (14:57 +0200)
committerDavid Woodhouse <David.Woodhouse@intel.com>
Mon, 23 Mar 2009 13:13:55 +0000 (13:13 +0000)
panic_write may read in an interrupt context.

Signed-off-by: Adrian Hunter <adrian.hunter@nokia.com>
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
drivers/mtd/onenand/omap2.c

index 77a4f14461564043da7ee45bfd638bad5974a445..2c199b30ab58302dabac9e36905cec31efb4778b 100644 (file)
@@ -294,6 +294,10 @@ static int omap3_onenand_read_bufferram(struct mtd_info *mtd, int area,
        if (bram_offset & 3 || (size_t)buf & 3 || count < 384)
                goto out_copy;
 
+       /* panic_write() may be in an interrupt context */
+       if (in_interrupt())
+               goto out_copy;
+
        if (buf >= high_memory) {
                struct page *p1;