From: Damir Shayhutdinov <lost404@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: [PATCH] [JFFS2] Fix free space leaking
Date: Tue, 13 Nov 2007 13:23:23 +0300 [thread overview]
Message-ID: <20071113102323.GA5933@damir.rnd.local> (raw)
This patch is addressed to fix very-long-standing problem in JFFS2,
first described in 2004:
http://lists.infradead.org/pipermail/linux-mtd/2004-March/009456.html
jffs2_link_node_ref() decreases c->free_size by
c->cleanmarker_size but the clean marker space can't
be accounted as free space! So we just compensate
the difference.
Signed-off-by: Alexander Yurchenko <grange@tecon.ru>
Signed-off-by: Damir Shayhutdinov <damir@tecon.ru>
---
fs/jffs2/erase.c | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/fs/jffs2/erase.c b/fs/jffs2/erase.c
index a1db918..c574fa3 100644
--- a/fs/jffs2/erase.c
+++ b/fs/jffs2/erase.c
@@ -454,6 +454,17 @@ static void jffs2_mark_erased_block(struct jffs2_sb_info *c, struct jffs2_eraseb
jeb->free_size = c->sector_size;
/* FIXME Special case for cleanmarker in empty block */
jffs2_link_node_ref(c, jeb, jeb->offset | REF_NORMAL, c->cleanmarker_size, NULL);
+ /*
+ * XXX: I'm not sure this is correct but it prevents
+ * c->free_size from slow leaking under a frequent file
+ * overwriting.
+ * jffs2_link_node_ref() decreases c->free_size by
+ * c->cleanmarker_size but the clean marker space can't
+ * be accounted as free space! So we just compensate
+ * the difference.
+ */
+ c->free_size += c->cleanmarker_size;
+ c->used_size -= c->cleanmarker_size;
}
down(&c->erase_free_sem);
--
1.5.3.4.GIT
next reply other threads:[~2007-11-13 10:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 10:23 Damir Shayhutdinov [this message]
2008-02-06 10:20 ` [PATCH] [JFFS2] Fix free space leaking Joakim Tjernlund
2008-02-06 18:48 ` Damir Shayhutdinov
2008-02-21 11:11 ` Jörn Engel
2008-02-21 11:39 ` David Woodhouse
2008-04-03 9:03 ` Martin Creutziger
2008-04-22 23:16 ` David Woodhouse
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=20071113102323.GA5933@damir.rnd.local \
--to=lost404@gmail.com \
--cc=linux-mtd@lists.infradead.org \
/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