On Fri, Apr 22, 2011 at 10:23:14AM +0900, Tsutomu Itoh wrote: > But, reading code again, I noticed nobody use relocate_one_extent() now. ;-) > However, because there is a possibility to be going to be used in the future, > I'll add the check of 'new_extents' for the readability.
vim hilight confused me, but the function is inside a large #if 0 block already, I think we do not need to fix this kmalloc anymore. sorry for not pointing it out. the #if0 comes from commit 5d4f98a28c7d334091c1b7744f48a1acdd2a4ae0 dated back to Jun 10 10:45:14 2009 -0400 Btrfs: Mixed back reference (FORWARD ROLLING FORMAT CHANGE) big changeset, disk format change, it's quite understandable that the autors wanted to keep the previous code in place for some time, but it's not needed anymore. david -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
