The patch titled
     ext2 balloc: use io_error label
has been removed from the -mm tree.  Its filename was
     ext2-balloc-use-io_error-label.patch

This patch was dropped because it was folded into ext2-reservations.patch

------------------------------------------------------
Subject: ext2 balloc: use io_error label
From: Hugh Dickins <[EMAIL PROTECTED]>

ext2_new_blocks has a nice io_error label for setting -EIO, so goto that in
the one place that doesn't already use it.

Signed-off-by: Hugh Dickins <[EMAIL PROTECTED]>
Cc: Martin Bligh <[EMAIL PROTECTED]>
Acked-by: Mingming Cao <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---

 fs/ext2/balloc.c |    7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff -puN fs/ext2/balloc.c~ext2-balloc-use-io_error-label fs/ext2/balloc.c
--- a/fs/ext2/balloc.c~ext2-balloc-use-io_error-label
+++ a/fs/ext2/balloc.c
@@ -1297,10 +1297,9 @@ retry_alloc:
                if (group_no >= ngroups)
                        group_no = 0;
                gdp = ext2_get_group_desc(sb, group_no, &gdp_bh);
-               if (!gdp) {
-                       *errp = -EIO;
-                       goto out;
-               }
+               if (!gdp)
+                       goto io_error;
+
                free_blocks = le16_to_cpu(gdp->bg_free_blocks_count);
                /*
                 * skip this group if the number of
_

Patches currently in -mm which might be from [EMAIL PROTECTED] are

origin.patch
lib-percpu_counter_sub.patch
mm-per-device-dirty-threshold.patch
ext2-reservations.patch
ext2-balloc-use-io_error-label.patch
memory-controller-memory-accounting-v7-fix-swapoff-breakage-however.patch
exportfs-add-fid-type.patch
exportfs-add-new-methods.patch
shmem-new-export-ops.patch
exportfs-remove-old-methods.patch
exportfs-make-struct-export_operations-const.patch
exportfs-update-documentation.patch
prio_tree-debugging-patch.patch

-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to