public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: linux-kernel@vger.kernel.org
Subject: 2.4.21pre5aa2
Date: Sat, 15 Mar 2003 06:05:03 +0100	[thread overview]
Message-ID: <20030315050503.GA1252@dualathlon.random> (raw)

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

                 reply	other threads:[~2003-03-15  4:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030315050503.GA1252@dualathlon.random \
    --to=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox