From: Oleg Drokin <green@namesys.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org, reiserfs-dev@namesys.com
Subject: Re: [reiserfs-dev] Re: [PATCH] certain data corruption may cause reiserfs to panic, fix.
Date: Fri, 11 Jan 2002 12:45:12 +0300 [thread overview]
Message-ID: <20020111124512.F17925@namesys.com> (raw)
In-Reply-To: <20020109162207.A15139@namesys.com> <Pine.LNX.4.21.0201091458360.21044-100000@freak.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0201091458360.21044-100000@freak.distro.conectiva>
Hello!
On Wed, Jan 09, 2002 at 02:58:45PM -0200, Marcelo Tosatti wrote:
> > Purpose of this patch is to catch events of corrupted ITEM_TYPE fields, and report these to user.
> > Without this patch, accessing such items will resukt in dereferencing random memory areas in kernel,
> > and then ooping (most probably).
> > Please apply.
> Why corruption is happening in the first place ?
As Chris already pointed out, there was a problem with old gcc 2.96.
Also such corruptions might be a fault of a disk, somebody carelessly writing data to reiserfsdisk and so on.
Right now it is way too easy to get reiserfs to panic by mounting specially crafted abd disk image, and this is
bad, I believe, so one of the tasks I am performing is to minimalize such cases. (look at ext2 as an example goal I want to achieve
some time in the future)
Bye,
Oleg
prev parent reply other threads:[~2002-01-11 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 13:22 [PATCH] certain data corruption may cause reiserfs to panic, fix Oleg Drokin
2002-01-09 16:58 ` Marcelo Tosatti
[not found] ` <Pine.LNX.4.21.0201091458360.21044-100000@freak.distro.conectiva >
2002-01-09 20:52 ` Chris Mason
2002-01-11 9:45 ` Oleg Drokin [this message]
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=20020111124512.F17925@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