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.6.5-rc3-aa1
Date: Wed, 31 Mar 2004 05:09:21 +0200	[thread overview]
Message-ID: <20040331030921.GA2143@dualathlon.random> (raw)

The xfs warning during truncate will be fixed with a later update
(Nathan is currently working on it).

next thing to do is to fixup the merging in mprotect.

In the meantime this is already mergeable in -mm if Andrew is
interested.

I'm not touching mremap at this time (i'll reistantiate the merging in
mprotect first, then Hugh testcase will work as well as in mainline). I
wait comments on the truncate/mremap race fixes (they clearly partly
collides with prio-tree but part of them seems shareable). That race
isn't trivial to fix but at the same time it doesn't worry me much right
now. I could add the semaphore, but mremap is an extreme fast path for
some workload like apache, so I'm not going to risk a
scalability-slowdown in there with an obviously safe patch of taking the
i_shared_sem semaphore, because even if that race triggers the kernel
shouldn't crash anymore.

URL:
	http://www.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.6/2.6.5-rc3-aa1.gz
	http://www.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.6/2.6.5-rc3-aa1/

Changelog diff between 2.6.5-rc2-aa6 and 2.6.5-rc3-aa1:

Files 2.6.5-rc2-aa6/anon-vma.gz and 2.6.5-rc3-aa1/anon-vma.gz differ

	Track anonymous pages generated by cows on dma regions
	(bug spotted by Hugh Dickins).

Files 2.6.5-rc2-aa6/extraversion and 2.6.5-rc3-aa1/extraversion differ

	Rediffed.

Only in 2.6.5-rc3-aa1: initramfs-search-for-init

	Initramfs handy patch from -mm.

Files 2.6.5-rc2-aa6/prio-tree.gz and 2.6.5-rc3-aa1/prio-tree.gz differ

	Fix xfs to check nonlinear mappings too.

	Fix x86-64 compilation.

Only in 2.6.5-rc3-aa1: tag-writeback-pages-fix.patch.gz

	Avoid crashes in rw_swap_page_sync due -mm writeback changes,
	final (more highlevel) fix from Andrew.



             reply	other threads:[~2004-03-31  3:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-31  3:09 Andrea Arcangeli [this message]
2004-03-31  3:41 ` 2.6.5-rc3-aa1 Andrew Morton
2004-03-31  4:08   ` 2.6.5-rc3-aa1 Andrea Arcangeli
2004-03-31 19:16 ` 2.6.5-rc3-aa1 Bongani Hlope
2004-03-31 21:22   ` 2.6.5-rc3-aa1 Andrea Arcangeli
2004-04-01  4:47     ` 2.6.5-rc3-aa1 Bongani Hlope
2004-04-01  9:57   ` 2.6.5-rc3-aa1 Marc-Christian Petersen
2004-04-01 10:21     ` 2.6.5-rc3-aa1 Marc-Christian Petersen
2004-04-01 19:00       ` 2.6.5-rc3-aa1 Bongani Hlope
2004-04-01 13:38     ` 2.6.5-rc3-aa1 Andrea Arcangeli

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=20040331030921.GA2143@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