Hello Jiang, On Fri, Jun 07, 2013 at 12:07:22AM +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. Sorry for bothering you with description nitpick. I agree your approach is so simple that I'd like to give Ack but your description is not clear. If you really want to say deadlock issue with flipping approach, please add enough explain how the deadlock happens.(But not sure it is worth that we should keep the problem of deadlock issue of flipping approach in changelog) Otherwise, it's enough with first paragraph because this bug is very simple and plain. I prefer latter because I want that other developers don't waste their time to understand a deadlock issue of flipping approach) > > So fix it by holding an extra reference to zram->disk before calling > destroy_device(zram). > > Signed-off-by: Jiang Liu <jiang.liu@xxxxxxxxxx> > Cc: stable@xxxxxxxxxxxxxxx Acked-by: Minchan Kim <minchan@xxxxxxxxxx> But please rewrite the description. -- Kind regards, Minchan Kim _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
