On 08/03/2017 11:25 AM, Wang Shilong wrote:
On Thu, Aug 3, 2017 at 11:00 PM, Chris Mason wrote:
On 07/27/2017 02:52 PM, fdman...@kernel.org wrote:
From: Filipe Manana
If the range being cleared was not marked for defrag and we are not
about to clear the range from the defrag status, we
On Thu, Aug 3, 2017 at 11:00 PM, Chris Mason wrote:
>
>
> On 07/27/2017 02:52 PM, fdman...@kernel.org wrote:
>>
>> From: Filipe Manana
>>
>> If the range being cleared was not marked for defrag and we are not
>> about to clear the range from the defrag status, we don't need to
>> lock and unlock
On 07/27/2017 02:52 PM, fdman...@kernel.org wrote:
From: Filipe Manana
If the range being cleared was not marked for defrag and we are not
about to clear the range from the defrag status, we don't need to
lock and unlock the inode.
Signed-off-by: Filipe Manana
Thanks Filipe, looks like it
From: Filipe Manana
If the range being cleared was not marked for defrag and we are not
about to clear the range from the defrag status, we don't need to
lock and unlock the inode.
Signed-off-by: Filipe Manana
---
fs/btrfs/inode.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
d