diff options
author | Filipe Manana <fdmanana@suse.com> | 2020-09-14 11:01:04 +0300 |
---|---|---|
committer | David Sterba <dsterba@suse.com> | 2020-09-14 18:27:16 +0300 |
commit | 1c78544eaa4660096aeb6a57ec82b42cdb3bfe5a (patch) | |
tree | da7a2e73d516f9401062f9e82f34dfa351513af1 /fs/fs-writeback.c | |
parent | 2d892ccdc163a3d2e08c5ed1cea8b61bf7e4f531 (diff) | |
download | linux-1c78544eaa4660096aeb6a57ec82b42cdb3bfe5a.tar.xz |
btrfs: fix wrong address when faulting in pages in the search ioctl
When faulting in the pages for the user supplied buffer for the search
ioctl, we are passing only the base address of the buffer to the function
fault_in_pages_writeable(). This means that after the first iteration of
the while loop that searches for leaves, when we have a non-zero offset,
stored in 'sk_offset', we try to fault in a wrong page range.
So fix this by adding the offset in 'sk_offset' to the base address of the
user supplied buffer when calling fault_in_pages_writeable().
Several users have reported that the applications compsize and bees have
started to operate incorrectly since commit a48b73eca4ceb9 ("btrfs: fix
potential deadlock in the search ioctl") was added to stable trees, and
these applications make heavy use of the search ioctls. This fixes their
issues.
Link: https://lore.kernel.org/linux-btrfs/632b888d-a3c3-b085-cdf5-f9bb61017d92@lechevalier.se/
Link: https://github.com/kilobyte/compsize/issues/34
Fixes: a48b73eca4ceb9 ("btrfs: fix potential deadlock in the search ioctl")
CC: stable@vger.kernel.org # 4.4+
Tested-by: A L <mail@lechevalier.se>
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/fs-writeback.c')
0 files changed, 0 insertions, 0 deletions