From: Shen Feng <shen@cn.fujitsu.com>
To: linux-ext4@vger.kernel.org, Theodore Tso <tytso@MIT.EDU>,
Mingming Cao <cmm@us.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH] ext4: Fix the loop condition in ext4_mb_free_committed_blocks
Date: Wed, 11 Jun 2008 11:55:45 +0800 [thread overview]
Message-ID: <484F4CC1.3000109@cn.fujitsu.com> (raw)
Since md is freed before the do-while checks it,
it's better to change it to while(1).
Signed-off-by: Shen Feng <shen@cn.fujitsu.com>
---
fs/ext4/mballoc.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
index 42553f6..063f820 100644
--- a/fs/ext4/mballoc.c
+++ b/fs/ext4/mballoc.c
@@ -2572,7 +2572,7 @@ ext4_mb_free_committed_blocks(struct super_block *sb)
kfree(md);
ext4_mb_release_desc(&e4b);
- } while (md);
+ } while (1);
mb_debug("freed %u blocks in %u structures\n", count, count2);
}
--
1.5.4.5
next reply other threads:[~2008-06-11 3:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 3:55 Shen Feng [this message]
2008-06-11 11:34 ` [PATCH] ext4: Fix the loop condition in ext4_mb_free_committed_blocks Aneesh Kumar K.V
2008-06-11 14:23 ` Theodore Tso
2008-06-12 2:57 ` [PATCH V2] " Shen Feng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=484F4CC1.3000109@cn.fujitsu.com \
--to=shen@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@MIT.EDU \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).