The patch titled
Subject: ocfs2-try-to-reuse-extent-block-in-dealloc-without-meta_alloc-fix
has been removed from the -mm tree. Its filename was
ocfs2-try-to-reuse-extent-block-in-dealloc-without-meta_alloc-fix.patch
This patch was dropped because it was folded into ocfs2-try-to-reuse-extent-block-in-dealloc-without-meta_alloc.patch
------------------------------------------------------
From: Changwei Ge <ge.changwei@xxxxxxx>
Subject: ocfs2-try-to-reuse-extent-block-in-dealloc-without-meta_alloc-fix
fix static checker warnning
Link: http://lkml.kernel.org/r/63ADC13FD55D6546B7DECE290D39E373F29196AE@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Signed-off-by: Changwei Ge <ge.changwei@xxxxxxx>
Reported-by: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
Cc: John Lightsey <john@xxxxxxxxxxx>
Cc: Joel Becker <jlbec@xxxxxxxxxxxx>
Cc: Joseph Qi <jiangqi903@xxxxxxxxx>
Cc: Junxiao Bi <junxiao.bi@xxxxxxxxxx>
Cc: Mark Fasheh <mfasheh@xxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/ocfs2/alloc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN fs/ocfs2/alloc.c~ocfs2-try-to-reuse-extent-block-in-dealloc-without-meta_alloc-fix fs/ocfs2/alloc.c
--- a/fs/ocfs2/alloc.c~ocfs2-try-to-reuse-extent-block-in-dealloc-without-meta_alloc-fix
+++ a/fs/ocfs2/alloc.c
@@ -6756,8 +6756,8 @@ static int ocfs2_reuse_blk_from_dealloc(
*blk_given = i;
bail:
- if (unlikely(status)) {
- for (; i >= 0; i--) {
+ if (unlikely(status < 0)) {
+ for (i = 0; i < blk_wanted; i++) {
if (new_eb_bh[i])
brelse(new_eb_bh[i]);
}
_
Patches currently in -mm which might be from ge.changwei@xxxxxxx are
ocfs2-dlm-clean-dead-code-up.patch
ocfs2-cluster-neaten-a-member-of-o2net_msg_handler.patch
ocfs2-clean-dead-code-in-suballocc.patch
ocfs2-clean-dead-code-up-in-allocc.patch
ocfs2-make-metadata-estimation-accurate-and-clear.patch
ocfs2-try-to-reuse-extent-block-in-dealloc-without-meta_alloc.patch
ocfs2-unlock-bh_state-if-bg-check-fails.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
