public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Xuan Baldauf <xuan--reiserfs@baldauf.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Nicholas Petreley <nicholas@petreley.com>,
	Harald Dunkel <harri@synopsys.COM>,
	linux-kernel@vger.kernel.org
Subject: Re: ReiserFS? How reliable is it? Is this the future?
Date: Thu, 05 Apr 2001 03:05:56 +0200	[thread overview]
Message-ID: <3ACBC4F4.C177E40A@baldauf.org> (raw)
In-Reply-To: <E14kU75-0008Qx-00@the-village.bc.nu>



Alan Cox wrote:

> > The bad (2.2 kernels)
> >
> > * Nothing I can think of
>
> Security exploit according to bugtraq, but Im pretty sure it wont take Chris
> Mason and friends long to fix that.
>

This is a reiserfs security issue, but only of theoretical nature (Even if
triggered, it won't harm you). But the reason for this bug is in NFS (v2, v3,
hopefully not also v4) readdir braindamage.

I think, in Reiser(FS)4, a more sophisticated (NFS-)work-around (horizontal
displacement instead of vertical displacement) is planned.

I can tell you more if you want.

Xuân.



  reply	other threads:[~2001-04-05  1:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-03 12:13 ReiserFS? How reliable is it? Is this the future? Harald Dunkel
2001-04-03 12:47 ` Frank Fiene
2001-04-03 16:19 ` Nicholas Petreley
2001-04-03 16:57   ` Alan Cox
2001-04-05  1:05     ` Xuan Baldauf [this message]
2001-04-05  1:13       ` Alan Cox
2001-04-05  1:23         ` Xuan Baldauf
2001-04-05 13:52         ` [PATCH] reiserfs old data bug 2.2.x (was: ReiserFS? How reliable ...) Chris Mason
2001-04-03 18:23 ` ReiserFS? How reliable is it? Is this the future? jury gerold
2001-04-03 22:15 ` Shawn Starr
2001-04-04 10:18 ` Ookhoi

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=3ACBC4F4.C177E40A@baldauf.org \
    --to=xuan--reiserfs@baldauf.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=harri@synopsys.COM \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicholas@petreley.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