On Wed, 19 Jun 2013, Sage Weil wrote:
> Hi Chris,
>
> On Tue, 18 Jun 2013, Chris Mason wrote:
> > [...]
> > Very long way of saying I think we're one release_path short. Sage, I
> > haven't tested this at all yet, I was hoping to trigger it first.
> >
> > diff --git a/fs/btrfs/tree-log.c b/fs/btrfs/tree-log.c
> > index c276ac9..c1954b3 100644
> > --- a/fs/btrfs/tree-log.c
> > +++ b/fs/btrfs/tree-log.c
> > @@ -3730,6 +3730,7 @@ next_slot:
> > log_extents:
> > if (fast_search) {
> > btrfs_release_path(dst_path);
> > + btrfs_release_path(path);
> > ret = btrfs_log_changed_extents(trans, root, inode, dst_path);
> > if (ret) {
> > err = ret;
>
> This seems to be doing the trick. I'll keep testing overnight, but so far
> so good!
...and it's still holding up well in QA.
Thanks, Chris!
sage
--
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
