From: Oleg Drokin <green@namesys.com>
To: marcelo@conectiva.com.br, linux-kernel@vger.kernel.org,
reiserfs-dev@namesys.com
Subject: [2.4] [PATCH] Make reiserfs to refuse mounting of non 4K blocksize filesystems
Date: Thu, 31 Oct 2002 13:05:17 +0300 [thread overview]
Message-ID: <20021031130517.A13414@namesys.com> (raw)
Hello!
There seems to be some confusion going on among the users who try
to use non-standard blocksize reiserfs filesystems with 2.4 kernels
(where this support is not yet merged) and are able to easily crash
kernel this way, so it seems following patch is necessary for now,
that only allows to mount 4K-blocksize reiserfs filesystems.
Please apply.
Thank you.
Bye,
Oleg
===== fs/reiserfs/super.c 1.26 vs edited =====
--- 1.26/fs/reiserfs/super.c Thu Sep 12 12:39:21 2002
+++ edited/fs/reiserfs/super.c Wed Oct 30 16:42:36 2002
@@ -863,6 +863,12 @@
s->s_blocksize_bits ++;
brelse (bh);
+
+ if (s->s_blocksize != 4096) {
+ printk("Unsupported reiserfs blocksize: %ld on %s, only 4096 bytes "
+ "blocksize is supported.\n", s->s_blocksize, kdevname (s->s_dev));
+ return 1;
+ }
if (s->s_blocksize != size)
set_blocksize (s->s_dev, s->s_blocksize);
reply other threads:[~2002-10-31 9:58 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=20021031130517.A13414@namesys.com \
--to=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=reiserfs-dev@namesys.com \
/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