public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: adilger@clusterfs.com
Cc: quintela@mandrakesoft.com, fmfkrauss@mindspring.com,
	linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net,
	marcelo@conectiva.com.br
Subject: Re: [PATCH] Possible EXT2 File System Corruption in Kernel 2.4
Date: Mon, 20 May 2002 21:02:20 -0700 (PDT)	[thread overview]
Message-ID: <20020520.210220.99529819.davem@redhat.com> (raw)
In-Reply-To: <20020521035702.GA9901@turbolinux.com>

   From: Andreas Dilger <adilger@clusterfs.com>
   Date: Mon, 20 May 2002 21:57:02 -0600

   It is likely that block is being set as -EPERM or something like that,
   but I'm not sure.

Interesting analysis.

However, I walked over this code a few times and I cannot
find a way that -EPERM can land there.

What might be happening, instead, is that due to some bug
in ext2_alloc_block we end up with -1 as the answer.  It
would be useful to add some debugging there to see if the
return value 'j' is ever -1 when we set *err to '0'.

  reply	other threads:[~2002-05-21  4:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E16vKwg-00056q-00@barry.mail.mindspring.net>
2002-04-11 16:40 ` Possible EXT2 File System Corruption in Kernel 2.4 Frank Krauss
2002-04-11 19:12   ` [PATCH] " Andreas Dilger
2002-04-11 20:10     ` Andrew Morton
2002-04-17  7:56   ` [PATCH] " Andreas Dilger
2002-05-20  9:38     ` Juan Quintela
2002-05-21  3:57       ` Andreas Dilger
2002-05-21  4:02         ` David S. Miller [this message]
2002-04-17 17:31 Marc-Christian Petersen
     [not found] <20020417170758.8070026884@smtp.clusterfs.com>
2002-04-17 18:33 ` Andreas Dilger

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=20020520.210220.99529819.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=adilger@clusterfs.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=fmfkrauss@mindspring.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=quintela@mandrakesoft.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