From: Oleg Drokin <green@namesys.com>
To: Jakob Oestergaard <jakob@unthought.net>,
linux-kernel@vger.kernel.org, Hans Reiser <reiser@namesys.com>
Subject: Re: ReiserFS buglet
Date: Tue, 24 Sep 2002 13:21:10 +0400 [thread overview]
Message-ID: <20020924132110.A22362@namesys.com> (raw)
In-Reply-To: <20020924072455.GE2442@unthought.net>
Hello!
On Tue, Sep 24, 2002 at 09:24:55AM +0200, Jakob Oestergaard wrote:
> In linux-2.4.19, I found the following:
> fs/reiserfs/super.c:707
> s->s_blocksize = sb_blocksize(rs);
> s->s_blocksize_bits = 0;
> while ((1 << s->s_blocksize_bits) != s->s_blocksize)
> s->s_blocksize_bits ++;
> What happens if there's a bit-flip on the disk so that s->s_blocksize is
> not a power of two ?
FS will refuse to mount. Or kernel will panic (depends on some stuff).
If s->s_blocksize is zeroed, kernel will hang, as you correctly noticed.
> I would suggest replacing the '!=' with a '<' in the while loop and
> adding a sanity check afterwards.
What if overheated CPU will cause a bitflip exactly after such checks?
You cannot protect against broken hardware. Such problems should be
fixed by fsck.
> As I see it, the ReiserFS journal has the same problems as jbd wrt. to
> atomicity of write operations of indexes. Please see my recent mail
> about the jbd problems.
journal header in reiserfs only occupies first 20 bytes of the block,
since this fells within 1st 512 bytes hardware sector, it will be written
atomically, I presume.
Bye,
Oleg
next prev parent reply other threads:[~2002-09-24 9:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 7:24 ReiserFS buglet Jakob Oestergaard
2002-09-24 9:21 ` Oleg Drokin [this message]
2002-09-24 9:27 ` Jakob Oestergaard
2002-09-24 9:42 ` Hans Reiser
2002-09-24 9:47 ` Jakob Oestergaard
2002-09-24 9:48 ` Oleg Drokin
2002-09-24 10:03 ` Jakob Oestergaard
2002-09-24 10:25 ` Oleg Drokin
2002-09-24 10:39 ` Jakob Oestergaard
2002-09-24 10:54 ` Oleg Drokin
2002-09-24 11:30 ` Hans Reiser
2002-09-24 11:35 ` Oleg Drokin
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=20020924132110.A22362@namesys.com \
--to=green@namesys.com \
--cc=jakob@unthought.net \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.