From: jing zhang <zj.barak@gmail.com>
To: linux-ext4 <linux-ext4@vger.kernel.org>
Cc: "Theodore Ts'o" <tytso@mit.edu>, Andreas Dilger <adilger@sun.com>,
Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Subject: [PATCH] ext4: memory leakage in ext4_discard_preallocations
Date: Thu, 18 Mar 2010 20:39:40 +0800 [thread overview]
Message-ID: <ac8f92701003180539h7228040bm82a0c69d678ec93b@mail.gmail.com> (raw)
From: Jing Zhang <zj.barak@gmail.com>
Date: Thu Mar 18 20:33:44 2010
When unexpected errors occur, there is memory leakage, and more.
Cc: Theodore Ts'o <tytso@mit.edu>
Cc: Andreas Dilger <adilger@sun.com>
Cc: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Signed-off-by: Jing Zhang <zj.barak@gmail.com>
---
--- linux-2.6.32/fs/ext4/mballoc.c 2009-12-03 11:51:22.000000000 +0800
+++ zj/mballoc.c 2010-03-18 20:41:32.000000000 +0800
@@ -3717,6 +3717,7 @@ void ext4_discard_preallocations(struct
struct list_head list;
struct ext4_buddy e4b;
int err;
+ int occurs = 0;
if (!S_ISREG(inode->i_mode)) {
/*BUG_ON(!list_empty(&ei->i_prealloc_list));*/
@@ -3781,6 +3782,7 @@ repeat:
}
spin_unlock(&ei->i_prealloc_lock);
+best_efforts:
list_for_each_entry_safe(pa, tmp, &list, u.pa_tmp_list) {
BUG_ON(pa->pa_type != MB_INODE_PA);
ext4_get_group_no_and_offset(sb, pa->pa_pstart, &group, NULL);
@@ -3811,6 +3813,12 @@ repeat:
list_del(&pa->u.pa_tmp_list);
call_rcu(&(pa)->u.pa_rcu, ext4_mb_pa_callback);
}
+ if (! list_empty(&list)) {
+ if (occurs++ < 2)
+ goto best_efforts;
+ else
+ BUG();
+ }
if (ac)
kmem_cache_free(ext4_ac_cachep, ac);
}
next reply other threads:[~2010-03-18 12:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 12:39 jing zhang [this message]
2010-03-18 17:46 ` [PATCH] ext4: memory leakage in ext4_discard_preallocations tytso
2010-03-19 14:17 ` jing zhang
2010-03-19 17:27 ` Andreas Dilger
2010-03-20 14:05 ` jing zhang
2010-03-26 8:37 ` Aneesh Kumar K. V
2010-03-26 14:12 ` jing zhang
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=ac8f92701003180539h7228040bm82a0c69d678ec93b@mail.gmail.com \
--to=zj.barak@gmail.com \
--cc=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=shaggy@linux.vnet.ibm.com \
--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).