At 01/03/2017 12:47 AM, David Sterba wrote:
On Fri, Dec 30, 2016 at 09:00:36AM +0800, Qu Wenruo wrote:
Hi, please fetch the following branch for next branch:
https://github.com/adam900710/linux.git fujitsu_for_next
This branch contains most of Fujitsu unmerged patches for for-next branch.
Latest David's for-next-20161219 branch can cause kernel panic so I don't
use it as base, but v4.10-rc1.
The for-next branch will be reassembled again as we're past rc1 now.
I ran the full xfstests test cases, with both default mount options and
compress=lzo options.
Fixes are working and no new regression.
So I thing it should be good enough to act as a base for for-next branch.
This big patch set contains the following fixes:
1) Wang's fixes for compression ENOSPC
AFAIK, the patches have been reviewed only partially and used to be part
of for-next until the merge conflicts became unbearable. Patches
touching space handling need review before merging and at least some
sort of ack in case of for-next.
2) Qgroup reserved space fix and WARN_ON
Similar situation here.
Hopes comments from Chandan would help to merge some of the qgroup patches.
(I just forgot to add his tags, sorry Chandan)
btrfs: qgroup: Introduce extent changeset for qgroup reserve functions
https://patchwork.kernel.org/patch/9457621/
Reviewed-by: Chandan Rajendra <chan...@linux.vnet.ibm.com>
btrfs: qgroup: Fix qgroup reserved space underflow by only freeing
reserved ranges
https://patchwork.kernel.org/patch/9457619/
Reviewed-by: Chandan Rajendra <chan...@linux.vnet.ibm.com>
Tested-by: Chandan Rajendra <chan...@linux.vnet.ibm.com>
Thanks,
Qu
3) Inband dedupe work
As this is a new feature, I'll postpone it for now until the for-next
branch is settled after the merge window.
--
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
