xfs: fix freeing of inodes not yet added to the inode cache

When freeing an inode that lost race getting added to the inode cache we
must not call into ->destroy_inode, because that would delete the inode
that won the race from the inode cache radix tree.

This patch uses splits a new xfs_inode_free helper out of xfs_ireclaim
and uses that plus __destroy_inode to make sure we really only free
the memory allocted for the inode that lost the race, and not mess with
the inode cache state.

Signed-off-by: Christoph Hellwig <[email protected]>
Reviewed-by: Eric Sandeen <[email protected]>
Reported-by: Alex Samad <[email protected]>
Reported-by: Andrew Randrianasulu <[email protected]>
Reported-by: Stephane <[email protected]>
Reported-by: Tommy <[email protected]>
Reported-by: Miah Gregory <[email protected]>
Reported-by: Gabriel Barazer <[email protected]>
Reported-by: Leandro Lucarella <[email protected]>
Reported-by: Daniel Burr <[email protected]>
Reported-by: Nickolay <[email protected]>
Reported-by: Michael Guntsche <[email protected]>
Reported-by: Dan Carley <[email protected]>
Reported-by: Michael Ole Olsen <[email protected]>
Reported-by: Michael Weissenbacher <[email protected]>
Reported-by: Martin Spott <[email protected]>
Reported-by: Christian Kujau <[email protected]>
Tested-by: Michael Guntsche <[email protected]>
Tested-by: Dan Carley <[email protected]>
Tested-by: Christian Kujau <[email protected]>

0 files changed, 0 insertions, 0 deletions