All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>,
	Oleg Drokin <green@namesys.com>
Cc: linux-kernel@vger.kernel.org, reiserfs-dev@namesys.com
Subject: Re: [PATCH] certain data corruption may cause reiserfs to panic, fix.
Date: Wed, 09 Jan 2002 15:52:09 -0500	[thread overview]
Message-ID: <344590000.1010609528@tiny> (raw)
In-Reply-To: <Pine.LNX.4.21.0201091458360.21044-100000@freak.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0201091458360.21044-100000@freak.distro.conectiva >



On Wednesday, January 09, 2002 02:58:45 PM -0200 Marcelo Tosatti
<marcelo@conectiva.com.br> wrote:

> On Wed, 9 Jan 2002, Oleg Drokin wrote:
> 
>> Hello!
>> 
>>     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 ? 

Oddly, the corruption most often caught by this patch was from the early
redhat gcc 2.96.

-chris


  parent reply	other threads:[~2002-01-09 20:53 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 [this message]
2002-01-11  9:45   ` [reiserfs-dev] " 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=344590000.1010609528@tiny \
    --to=mason@suse.com \
    --cc=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 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.