[lkml]   [2001]   [Nov]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.4.15aa1
In article <1006629351.1470.8.camel@praetorian> asked:
| -=-=-=-=-=-
| On Sat, 2001-11-24 at 02:50, Andrea Arcangeli wrote:
| > Only in 2.4.15aa1: 00_iput-unmount-corruption-fix-1
| >
| > Fix iput umount corruption.
| Is this the problem that Al put out a patch for yesterday? And is his
| patch been tested and working?
| > Only in 2.4.15aa1: 00_read_super-stale-inode-1
| >
| > If read_super fails avoid lefting stale inodes queued into
| > the superblock.
| What is this? How dangerous is it?

Good question. As I read the patch, the problem occurs during umount,
when dirty inodes are not (properly) written to the disk. Would a sync()
help or eliminate this problem, assuming that all files were closed?
Hopefully someone knows, I don't want to tell you it only happens at
umount, but that's my impression.

In any case, since 2.4.16 is out (so much for "2.4.15 released without
embarrassment") to fix the problem, I would go with that unless you have
a reason to use whichever patch pleases you.

bill davidsen <>
His first management concern is not solving the problem, but covering
his ass. If he lived in the middle ages he'd wear his codpiece backward.
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:13    [W:0.073 / U:0.536 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site