summaryrefslogtreecommitdiff
path: root/fs/no-block.c
diff options
context:
space:
mode:
authorOmar Sandoval <osandov@fb.com>2017-08-11 09:00:06 -0700
committerDarrick J. Wong <darrick.wong@oracle.com>2017-08-11 16:56:33 -0700
commitc44245b3d5435f533ca8346ece65918f84c057f9 (patch)
treee68e72bf645789fce0a13b4606c6bf278f2795b9 /fs/no-block.c
parent56bdf855e676f1f2ed7033f288f57dfd315725ba (diff)
downloadlwn-c44245b3d5435f533ca8346ece65918f84c057f9.tar.gz
lwn-c44245b3d5435f533ca8346ece65918f84c057f9.zip
xfs: fix inobt inode allocation search optimization
When we try to allocate a free inode by searching the inobt, we try to find the inode nearest the parent inode by searching chunks both left and right of the chunk containing the parent. As an optimization, we cache the leftmost and rightmost records that we previously searched; if we do another allocation with the same parent inode, we'll pick up the search where it last left off. There's a bug in the case where we found a free inode to the left of the parent's chunk: we need to update the cached left and right records, but because we already reassigned the right record to point to the left, we end up assigning the left record to both the cached left and right records. This isn't a correctness problem strictly, but it can result in the next allocation rechecking chunks unnecessarily or allocating inodes further away from the parent than it needs to. Fix it by swapping the record pointer after we update the cached left and right records. Fixes: bd169565993b ("xfs: speed up free inode search") Signed-off-by: Omar Sandoval <osandov@fb.com> Reviewed-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Diffstat (limited to 'fs/no-block.c')
0 files changed, 0 insertions, 0 deletions