linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik van der Kouwe <vdkouwe@cs.vu.nl>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Fam Zheng <famcool@gmail.com>
Subject: [PATCH] fs/minix: bugfix, number of indirect block ptrs per block depends on block size
Date: Wed, 26 May 2010 12:03:23 +0200	[thread overview]
Message-ID: <4BFCF1EB.20709@cs.vu.nl> (raw)

From: Erik van der Kouwe <vdkouwe@cs.vu.nl>

The MINIX filesystem driver used a constant number of indirect block 
pointers in an indirect block. This worked only for filesystems with 1kb 
block, while the MINIX default block size is now 4kb. As a consequence, 
large files were read incorrectly on such filesystems and writing a 
large file would cause the filesystem to become corrupted. This patch 
computes the number of indirect block pointers based on the block size, 
making the driver work for each block size. 

I would like to thank Feiran Zheng ('Fam') for pointing out the cause 
of the corruption.

Signed-off-by: Erik van der Kouwe <vdkouwe@cs.vu.nl>
---

--- fs/minix/itree_v2.c.orig	2010-05-26 14:10:15.000000000 +0200
+++ fs/minix/itree_v2.c	2010-05-26 13:44:53.000000000 +0200
@@ -20,6 +20,9 @@ static inline block_t *i_data(struct ino
 	return (block_t *)minix_i(inode)->u.i2_data;
 }
 
+#define DIRCOUNT 7
+#define INDIRCOUNT(sb) ((sb)->s_blocksize / 4)
+
 static int block_to_path(struct inode * inode, long block, int offsets[DEPTH])
 {
 	int n = 0;
@@ -34,21 +37,21 @@ static int block_to_path(struct inode * 
 			printk("MINIX-fs: block_to_path: "
 			       "block %ld too big on dev %s\n",
 				block, bdevname(sb->s_bdev, b));
-	} else if (block < 7) {
+	} else if (block < DIRCOUNT) {
 		offsets[n++] = block;
-	} else if ((block -= 7) < 256) {
-		offsets[n++] = 7;
+	} else if ((block -= DIRCOUNT) < INDIRCOUNT(sb)) {
+		offsets[n++] = DIRCOUNT;
 		offsets[n++] = block;
-	} else if ((block -= 256) < 256*256) {
-		offsets[n++] = 8;
-		offsets[n++] = block>>8;
-		offsets[n++] = block & 255;
+	} else if ((block -= INDIRCOUNT(sb)) < INDIRCOUNT(sb) * INDIRCOUNT(sb)) {
+		offsets[n++] = DIRCOUNT + 1;
+		offsets[n++] = block / INDIRCOUNT(sb);
+		offsets[n++] = block % INDIRCOUNT(sb);
 	} else {
-		block -= 256*256;
-		offsets[n++] = 9;
-		offsets[n++] = block>>16;
-		offsets[n++] = (block>>8) & 255;
-		offsets[n++] = block & 255;
+		block -= INDIRCOUNT(sb) * INDIRCOUNT(sb);
+		offsets[n++] = DIRCOUNT + 2;
+		offsets[n++] = (block / INDIRCOUNT(sb)) / INDIRCOUNT(sb);
+		offsets[n++] = (block / INDIRCOUNT(sb)) % INDIRCOUNT(sb);
+		offsets[n++] = block % INDIRCOUNT(sb);
 	}
 	return n;
 }


             reply	other threads:[~2010-05-26 10:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26 10:03 Erik van der Kouwe [this message]
2010-05-26 21:54 ` [PATCH] fs/minix: bugfix, number of indirect block ptrs per block depends on block size Jan Kara
2010-05-27 16:01   ` Al Viro
2010-05-27 17:11   ` Erik van der Kouwe
2010-05-27 17:17     ` Jan Kara
2010-05-27  4:35 ` Al Viro

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=4BFCF1EB.20709@cs.vu.nl \
    --to=vdkouwe@cs.vu.nl \
    --cc=famcool@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).