From: Edward Shishkin <edward.shishkin@gmail.com>
To: ReiserFS Development mailing list <reiserfs-devel@vger.kernel.org>
Subject: [patch] reiser4: fix up cluster nodes accounting
Date: Tue, 16 Jul 2013 19:01:26 +0200 [thread overview]
Message-ID: <51E57C66.6070506@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #2: reiser4-fix-cluster-nodes-accounting.patch --]
[-- Type: text/x-patch, Size: 802 bytes --]
Problem:
Rare-occured oops when using transparent compression:
kernel BUG at fs/reiser4/block_alloc.c:151
The bug:
Incorrect accounting of nodes, occupied by cluster (ctail items group):
node, which contains the first item in the cluster wasn't take into account.
Fixup:
Increnent the counter of nodes, when the first item is found.
Signed-off-by: Edward Shishkin <edward.shishkin@gmail.com>
---
fs/reiser4/plugin/file/cryptcompress.c | 2 ++
1 file changed, 2 insertions(+)
--- linux-3.9.2.orig/fs/reiser4/plugin/file/cryptcompress.c
+++ linux-3.9.2/fs/reiser4/plugin/file/cryptcompress.c
@@ -816,6 +816,8 @@ static int find_cluster_item(hint_t * hi
/*
* item has been found in the current node
*/
+ dclust_inc_extension_ncount(hint);
+
return CBK_COORD_FOUND;
}
not_found:
reply other threads:[~2013-07-16 17:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=51E57C66.6070506@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=reiserfs-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).