summaryrefslogtreecommitdiffstats
path: root/fs/pstore/Makefile
diff options
context:
space:
mode:
authorDarrick J. Wong <darrick.wong@oracle.com>2017-11-22 21:21:07 +0100
committerDarrick J. Wong <darrick.wong@oracle.com>2017-11-27 18:33:25 +0100
commit98c4f78dcdd8cec112d1cbc5e9a792ee6e5ab7a6 (patch)
tree111e7c14e1d57dd1c7828fb760f08b5886a4daed /fs/pstore/Makefile
parentLinux 4.15-rc1 (diff)
downloadlinux-98c4f78dcdd8cec112d1cbc5e9a792ee6e5ab7a6.tar.xz
linux-98c4f78dcdd8cec112d1cbc5e9a792ee6e5ab7a6.zip
xfs: always free inline data before resetting inode fork during ifree
In xfs_ifree, we reset the data/attr forks to extents format without bothering to free any inline data buffer that might still be around after all the blocks have been truncated off the file. Prior to commit 43518812d2 ("xfs: remove support for inlining data/extents into the inode fork") nobody noticed because the leftover inline data after truncation was small enough to fit inside the inline buffer inside the fork itself. However, now that we've removed the inline buffer, we /always/ have to free the inline data buffer or else we leak them like crazy. This test was found by turning on kmemleak for generic/001 or generic/388. Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com> Reviewed-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'fs/pstore/Makefile')
0 files changed, 0 insertions, 0 deletions