* 2.4.21pre5aa2
@ 2003-03-15 5:05 Andrea Arcangeli
0 siblings, 0 replies; only message in thread
From: Andrea Arcangeli @ 2003-03-15 5:05 UTC (permalink / raw)
To: linux-kernel
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-03-15 4:54 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-03-15 5:05 2.4.21pre5aa2 Andrea Arcangeli
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox