On Thu, Jan 18, 2018 at 01:45:20PM +0200, Nikolay Borisov wrote: > > [95795.015577] R10: 00000000000006b4 R11: 0000000000000246 R12: > > 00007fa6791bae64 > > [95795.016569] R13: 0000000000000000 R14: 0000563386706210 R15: > > 00007ffccf0ab160 > > [95795.017662] Code: 00 00 00 4c 8b a3 98 25 00 00 49 83 bc 24 60 ff ff ff > > 00 75 16 49 83 bc 24 68 ff ff ff 00 75 0b 49 83 bc 24 70 ff ff ff 00 74 16 > > <0f> ff 49 8d b4 24 18 ff ff ff 31 c9 31 d2 48 89 df e8 93 7a ff > > [95795.020538] ---[ end trace e95877675c6ec00d ]--- > > [95795.021259] BTRFS info (device sdi): space_info 4 has 1072775168 free, > > is not full > > [95795.022390] BTRFS info (device sdi): space_info total=1073741824, > > used=114688, pinned=0, reserved=0, may_use=786432, readonly=65536 > > > > Fix this by ensuring the zero range operation does not call > > btrfs_truncate_block() if the corresponding extent is an unwritten one > > (it's pointless anyway, since reading from an unwritten extent yields > > zeroes). > > > > Signed-off-by: Filipe Manana <fdman...@suse.com>
Thanks. > This fixes the leaks me and Josef has seen so: > > Tested-by: Nikolay Borisov <nbori...@suse.com> Thanks. Added to current misc-next (that's going to be added to 4.16 queue after I let it pass through fstests). -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
