Hi,
here's one regression fix to TRIM ioctl. The range cannot be used as
its meaning can be confusing regarding physical and logical addresses.
This confusion in code led to potential corruptions when the range
overlapped data.
The original patch made it to several stable kernels and was promptly
reverted, the version for master branch is different due to additional
changes but the change is effectively the same.
Please pull, thanks.
----------------------------------------------------------------
The following changes since commit 06989c799f04810f6876900d4760c0edda369cf7:
Btrfs: fix race updating log root item during fsync (2019-05-28 19:26:46 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.2-rc4-tag
for you to fetch changes up to 8103d10b71610aa65a65d6611cd3ad3f3bd7beeb:
btrfs: Always trim all unallocated space in btrfs_trim_free_extents (2019-06-07 14:52:05 +0200)
----------------------------------------------------------------
Nikolay Borisov (1):
btrfs: Always trim all unallocated space in btrfs_trim_free_extents
fs/btrfs/extent-tree.c | 28 +++-------------------------
1 file changed, 3 insertions(+), 25 deletions(-)
The pull request you sent on Tue, 11 Jun 2019 18:16:28 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.2-rc4-tag
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6fa425a2651515f8d262f2c1d972c6632e7c941d
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/prtracker