This is a note to let you know that I've just added the patch titled

    Btrfs: cleanup orphan reservation if truncate fails

to the 3.8-stable tree which can be found at:
    
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     btrfs-cleanup-orphan-reservation-if-truncate-fails.patch
and it can be found in the queue-3.8 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.


>From 4a7d0f6854c4a4ad1dba00a3b128a32d39b9a742 Mon Sep 17 00:00:00 2001
From: Josef Bacik <[email protected]>
Date: Thu, 7 Feb 2013 16:27:28 -0500
Subject: Btrfs: cleanup orphan reservation if truncate fails

From: Josef Bacik <[email protected]>

commit 4a7d0f6854c4a4ad1dba00a3b128a32d39b9a742 upstream.

I noticed we were getting lots of warnings with xfstest 83 because we have
reservations outstanding.  This is because we moved the orphan add outside
of the truncate, but we don't actually cleanup our reservation if something
fails.  This fixes the problem and I no longer see warnings.  Thanks,

Signed-off-by: Josef Bacik <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 fs/btrfs/inode.c |    2 ++
 1 file changed, 2 insertions(+)

--- a/fs/btrfs/inode.c
+++ b/fs/btrfs/inode.c
@@ -2493,6 +2493,8 @@ int btrfs_orphan_cleanup(struct btrfs_ro
                                goto out;
 
                        ret = btrfs_truncate(inode);
+                       if (ret)
+                               btrfs_orphan_del(NULL, inode);
                } else {
                        nr_unlink++;
                }


Patches currently in stable-queue which might be from [email protected] are

queue-3.8/btrfs-cleanup-orphan-reservation-if-truncate-fails.patch
queue-3.8/btrfs-delete-inline-extents-when-we-find-them-during-logging.patch
queue-3.8/btrfs-account-for-orphan-inodes-properly-during-cleanup.patch
queue-3.8/btrfs-copy-everything-if-we-ve-created-an-inline-extent.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to