Hi Josef,
the commit is not in there, but the code looks like your post.
if (--trans->use_count) {
trans->block_rsv = trans->orig_rsv;
return 0;
}
trans->block_rsv = NULL;
while (count < 4) {
unsigned long cur = trans->delayed_ref_updates;
trans->delayed_ref_updates = 0;
But on the other hand I am quite new to git, how could I get your latest
commit?
Best Regards,
Martin
Am 16.09.2011 16:37, schrieb Josef Bacik:
On 09/16/2011 10:09 AM, Martin Mailand wrote:
Hi Josef,
after a quick test it seems that I do not hit this Warning any longer.
But I got a new one.
Hmm looks like that may not be my newest stuff, is commit
57f499e1bb76ba3ebeb09cd12e9dac84baa5812b
in there? Specifically look at __btrfs_end_transaction in transaction.c
and see if the line
trans->block_rsv = NULL;
is before the first while() loop. Thanks,
Josef
--
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
--
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
