Will this fix the potential possibility of 2.4.15 screwing my
system? (inode problem as people have been mentioning it, etc?)
Best regards,
Paulo
Andrea Arcangeli <andrea@suse.de> writes:
> Note: the "00_read_super-stale-inode-1" fix is under discussion with Al,
> but overall it should be just ok for public consumation (even if that
> are may change if we find any better alternative, at the moment I think
> it is better (cleaner, simpler and faster) alternative than the iput
> changes in function of the MS_ACTIVE info).
>
> URL:
>
> ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.15aa1.bz2
> ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.15aa1/
>
> Only in 2.4.15aa1: 00_iput-unmount-corruption-fix-1
>
> Fix iput umount corruption.
>
> Only in 2.4.15aa1: 00_read_super-stale-inode-1
>
> If read_super fails avoid lefting stale inodes queued into
> the superblock.
>
> Only in 2.4.15pre9aa1: 10_vm-16
> Only in 2.4.15aa1: 10_vm-17
>
> Dropped a leftover touch_buffer in bread (there's just one in getblk in
> -aa, and we need it in getblk [not only for reiserfs]).
>
> Andrea
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
-- Paulo J. Matos aka PDestroy : pocm(_at_)rnl.ist.utl.pt Instituto Superior Tecnico - Lisbon Software & Computer Engineering - A.I. - > http://www.rnl.ist.utl.pt/~pocm --- Yes, God had a deadline... So, He wrote it all in Lisp!- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Nov 30 2001 - 21:00:16 EST