From: Oleg Drokin <green@xxxxxxxxxxxxxx> Attempt to kfree(&info->mtd) is a bad idea since it's a different substructure in the middle of a properly allocated struct omap_nand_info. I guess nobody tripped it before since nobody really removes NAND flash and nobody unloads the module either. Signed-off-by: Oleg Drokin <green@xxxxxxxxxxxxxx> --- drivers/mtd/nand/omap2.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/mtd/nand/omap2.c b/drivers/mtd/nand/omap2.c index 4e33972..7c71716 100644 --- a/drivers/mtd/nand/omap2.c +++ b/drivers/mtd/nand/omap2.c @@ -1131,7 +1131,7 @@ static int omap_nand_remove(struct platform_device *pdev) /* Release NAND device, its internal structures and partitions */ nand_release(&info->mtd); iounmap(info->nand.IO_ADDR_R); - kfree(&info->mtd); + kfree(info); return 0; } -- 1.7.4 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
