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-aa5
Date: Thu, 8 Apr 2004 19:07:59 +0200	[thread overview]
Message-ID: <20040408170759.GI31667@dualathlon.random> (raw)

URL:

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

Changelog diff between 2.6.5-aa4 and 2.6.5-aa5:

Only in 2.6.5-aa5: nonlinear-can-do-mlock

	Avoid truncate vs nonlinear BUG mentioned by Hugh Dickins on l-k.
	Give nonlinear only to privilegied users that knows how to avoid
	breaking the kernel. If local security doesn't matter disable-cap-mlock
	can be enabled and it'll give mlock and remap-file-pages too to every
	user. truncate must be fixed anyways to increase the strength of
	disable-cap-mlock but it gets low priority after moving the thing under
	sysctl, and I plan to keep the nonlinear hack forever under the sysctl
	for VM robusteness in providing _fair_ swapping to all processes.
	BTW, the mmap(MAP_POPULATE) API is horrible, there's no way to catch
	a failure with it, it doesn't return any retval, and I cannot fix it
	in my tree or I become ABI/API incompatible with linux 2.6, that's just
	a broken API that wants to be fixed properly in mainline despite the
	break of backwards compatibility.

             reply	other threads:[~2004-04-08 17:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 17:07 Andrea Arcangeli [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-09 10:23 2.6.5-aa5 Marcus Hartig

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=20040408170759.GI31667@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