Revision adae52b94e18afa1f84fab67df2a8a872c2f5533 authored by Miao Xie on 31 March 2011, 09:43:23 UTC, committed by Chris Mason on 05 April 2011, 05:19:43 UTC
the object id of the space cache inode's key is allocated from the relative root, just like the regular file. So we can't identify space cache inode by checking the object id of the inode's key, and we have to clear __GFP_FS flag at the time we look up the space cache inode. Signed-off-by: Miao Xie <miaox@cn.fujitsu.com> Signed-off-by: Liu Bo <liubo2009@cn.fujitsu.com> Signed-off-by: Chris Mason <chris.mason@oracle.com>
1 parent 6e8df2a
Computing file changes ...