Hi Aneesh, Thanks for your reply. Aneesh Kumar K.V wrote:
We dropped the patch because I found that the double free in my case was not exactly due the explanation given in the patch above. I asked to drop the patch in http://article.gmane.org/gmane.comp.file-systems.ext4/10199 I also found that the patch is not completely correct. The meta-data blocks which are added to the free_list are not allocated from any prealloc space. So what you are seeing may be a different problem which the patch is hiding from happening. I guess you will have to look more closely at why the double-free is happening in your case. -aneesh
I thought that the problem would be solved if we check whether on-disk and buddy bitmap is different or not when inode prealloc space is released. However, my understanding was incorrect. I will continue examining this problem. Best regards, Kazuya Mio -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
