On Wed, Jun 05, 2013 at 12:06:00AM +0800, Jiang Liu wrote: > Memory for zram->disk object may have already been freed after returning > from destroy_device(zram), then it's unsafe for zram_reset_device(zram) > to access zram->disk again. > > We can't solve this bug by flipping the order of destroy_device(zram) > and zram_reset_device(zram), that will cause deadlock issues to the > zram sysfs handler.
What kinds of deadlock happen? Could you elaborate it more? -- Kind regards, Minchan Kim -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
