On Fri, 06 Sep 2013 10:36:48 +0200, Stefan Behrens wrote:
> On Fri, 06 Sep 2013 11:08:16 +0800, Miao Xie wrote:
>> On thu, 5 Sep 2013 16:58:43 +0200, Stefan Behrens wrote:
>>> The fact that btrfs_root_refs() returned 0 for the tree_root caused
>>> bugs in the past, therefore it is set to 1 with t
On Fri, 06 Sep 2013 11:08:16 +0800, Miao Xie wrote:
> Onthu, 5 Sep 2013 16:58:43 +0200, Stefan Behrens wrote:
>> The fact that btrfs_root_refs() returned 0 for the tree_root caused
>> bugs in the past, therefore it is set to 1 with this patch and
>> (hopefully) all affected code is adapted to t
On thu, 5 Sep 2013 16:58:43 +0200, Stefan Behrens wrote:
> The fact that btrfs_root_refs() returned 0 for the tree_root caused
> bugs in the past, therefore it is set to 1 with this patch and
> (hopefully) all affected code is adapted to this change.
>
> I verified this change by temporarily
The fact that btrfs_root_refs() returned 0 for the tree_root caused
bugs in the past, therefore it is set to 1 with this patch and
(hopefully) all affected code is adapted to this change.
I verified this change by temporarily adding WARN_ON() checks
everywhere where btrfs_root_refs() is used, chec