[lkml]   [2002]   [Feb]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [BUG] + [PATCH]: handling bad inodes in 2.4.x kernels
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.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:24    [W:0.070 / U:28.060 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site