From: Daniel Mack <daniel@yoobay.net>
To: Ken Brownfield <brownfld@irridia.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] + [PATCH]: handling bad inodes in 2.4.x kernels
Date: Fri, 15 Feb 2002 03:13:42 +0100 [thread overview]
Message-ID: <20020215031342.B19035@chaos.intra> (raw)
In-Reply-To: <20020213182927.I15910@chaos.intra> <20020214193319.C1518@asooo.flowerfire.com>
In-Reply-To: <20020214193319.C1518@asooo.flowerfire.com>; from brownfld@irridia.com on Thu, Feb 14, 2002 at 07:33:19PM -0600
On Thu, Feb 14, 2002 at 07:33:19PM -0600, Ken Brownfield wrote:
> One could argue that a corrupt filesystem is a corrupt filesystem, but
but a corrupted filesystem should not change the behaviour of the entire
kernel. write-opening a bad inode should not end up with the effect that
the rename() syscall does not work anymore, i wasn't even able to securely
shut down by box everytime that happend.
> I've seen this behavior first hand (without using debugfs,
> unfortunately).
thats how i found that bug - it exists in real life.
> I think it's worth someone with filesystem fu taking a
> look at this patch. Or "seconded", whatever. :)
there's another possibilty for fixing this in my latest posting.
daniel
prev parent reply other threads:[~2002-02-15 2:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 17:29 [BUG] + [PATCH]: handling bad inodes in 2.4.x kernels Daniel Mack
2002-02-15 1:33 ` Ken Brownfield
2002-02-15 2:13 ` Daniel Mack [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=20020215031342.B19035@chaos.intra \
--to=daniel@yoobay.net \
--cc=brownfld@irridia.com \
--cc=linux-kernel@vger.kernel.org \
/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.