From: Jakob Oestergaard <jakob@unthought.net>
To: Oleg Drokin <green@namesys.com>
Cc: linux-kernel@vger.kernel.org, Hans Reiser <reiser@namesys.com>
Subject: Re: ReiserFS buglet
Date: Tue, 24 Sep 2002 11:27:20 +0200 [thread overview]
Message-ID: <20020924092720.GF2442@unthought.net> (raw)
In-Reply-To: <20020924132110.A22362@namesys.com>
On Tue, Sep 24, 2002 at 01:21:10PM +0400, Oleg Drokin wrote:
> Hello!
>
...
>
> > 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.
Disk errors are common. Software can also flip that bit.
But I agree that it shouldn't be something that commonly happens, and I
suppose it is acceptable for a filesystem to barf if it has been
corrupted by malicious software.
>
> > 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.
You presume wrong.
I posted to LKML about a month ago with some questions regarding exactly
this issue. I had a disk that worked on 128 byte atomic writes - a
standard IDE disk.
The conclusion was something like "we know jack about the disk's
internal logic" so we need consistency measures instead of relying on
anything from the disk.
--
................................................................
: jakob@unthought.net : And I see the elder races, :
:.........................: putrid forms of man :
: Jakob Østergaard : See him rise and claim the earth, :
: OZ9ABN : his downfall is at hand. :
:.........................:............{Konkhra}...............:
next prev parent reply other threads:[~2002-09-24 9:22 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
2002-09-24 9:27 ` Jakob Oestergaard [this message]
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=20020924092720.GF2442@unthought.net \
--to=jakob@unthought.net \
--cc=green@namesys.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox