2.4.21pre5aa2

From: Andrea Arcangeli (andrea@suse.de)
Date: Sat Mar 15 2003 - 00:05:03 EST


URL:

        http://www.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.21pre5aa2.gz
        http://www.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.21pre5aa2/

diff between 2.4.21pre5aa1 and 2.4.21pre5aa2:

Only in 2.4.21pre5aa1: 00_extraversion-20
Only in 2.4.21pre5aa2: 00_extraversion-21

        Rediffed.

Only in 2.4.21pre5aa1: 00_smp-timers-not-deadlocking-1
Only in 2.4.21pre5aa2: 00_smp-timers-not-deadlocking-2

        Fixed smp race in mod_timer() with a spinlock-by-hand, so it
        doesn't break all the callers. Thanks to Andrew to point it out.

Only in 2.4.21pre5aa1: 60_tux-timer_t-2.gz

        Was empty. (thanks Marc-Christian ;)

Only in 2.4.21pre5aa1: 9999_fsync-msync-async-errors-1

        Dropped, before it can be re-included this should be addressed:

        1) the write failures must be propagated to the mapping both for the
           metadata and the data for the write()s too, without requiring the bh
           to be collected by the vm before the info is propagated
        2) all writepages/prepare_write must set the mapping->error before
           unlocking the page

        Without those fixes it remains a best-effort, not 100% reliable in
        reporting async I/O errors, just like w/o the patch in the first place.

        Thanks to Andrew to point out the writepage race in vmscan (part of
        point 2).

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/



This archive was generated by hypermail 2b29 : Sat Mar 15 2003 - 22:00:42 EST