Files
android_kernel_xiaomi_sm8450/fs/btrfs
Miao Xie c933956ddf Btrfs: fix wrong lock range and write size in check_can_nocow()
The write range may not be sector-aligned, for example:

       |--------|--------|	<- write range, sector-unaligned, size: 2blocks
  |--------|--------|--------|  <- correct lock range, size: 3blocks

But according to the old code, we used the size of write range to calculate
the lock range directly, not considered the offset, we would get a wrong lock
range:

       |--------|--------|	<- write range, sector-unaligned, size: 2blocks
  |--------|--------|		<- wrong lock range, size: 2blocks

And besides that, the old code also had the same problem when calculating
the real write size. Correct them.

Signed-off-by: Miao Xie <miaox@cn.fujitsu.com>
Signed-off-by: Josef Bacik <jbacik@fb.com>
2014-03-10 15:17:00 -04:00
..
2014-01-28 13:19:50 -08:00
2013-11-11 22:03:19 -05:00
2008-09-25 11:04:06 -04:00
2013-03-14 14:57:10 -04:00
2013-11-11 22:03:19 -05:00
2013-02-01 14:24:23 -05:00
2014-03-10 15:16:51 -04:00
2014-03-10 15:15:51 -04:00
2014-03-10 15:15:51 -04:00
2014-01-29 07:06:27 -08:00
2014-01-29 07:06:27 -08:00