[lkml]   [2003]   [Mar]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread

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


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).

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:33    [W:0.119 / U:0.932 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site