From: Ian Campbell <ijc@hellion.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org,
stable-review@kernel.org, akpm@linux-foundation.org,
alan@lxorguk.ukuu.org.uk, Greg KH <gregkh@suse.de>,
Peter Zijlstra <peterz@infradead.org>,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [RFC] mlock/stack guard interaction fixup
Date: Sat, 21 Aug 2010 12:56:10 +0100 [thread overview]
Message-ID: <1282391770.29609.1223.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTimuP9cFvd4pfqy6=vixSMdagrSEv1-VLNAEuWgr@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]
On Fri, 2010-08-20 at 16:59 -0700, Linus Torvalds wrote:
> Ian (and others),
> here's a three-patch series that uses the doubly linked list to do
> your mlock() case hopefully correctly.
Thanks Linus.
> NOTE! It's untested. The first patch (which is the slightly scary one)
> is tested to some degree, the two other ones I checked that they
> compile, but that's it.
I applied on top of 2.6.35.3 and it fixes the simple test case I posted
yesterday as well as the original issue I was seeing with the Xen
toolstack on 2.6.32.20.
I don't know that they are particularly good tests for this change but I
also ran allmodconfig kernel build and ltp on 2.6.35.3+fixes without
issue. Are there any good mlock heavy workloads?
Out of interest, why is there no guard page for the VM_GROWSUP stack
case? Is it just that the memory layout on PA-RISC makes the stack grows
into the heap scenario impossible?
> I'm not going to apply them to my main tree unless they get testing
> and acks.
Tested-by: Ian Campbell <ijc@hellion.org.uk>
> And as mentioned, I've not done any of the changes that
> having a vm_prev pointer can allow in other places.
>
> Comments? Fixes? Braindamage?
>
> Linus
--
Ian Campbell
Providence, New Jersey, is one of the few cities where Velveeta cheese
appears on the gourmet shelf.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-08-21 11:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 23:59 Linus Torvalds
2010-08-21 0:20 ` Mike Snitzer
2010-08-21 0:54 ` Linus Torvalds
2010-08-21 11:56 ` Ian Campbell [this message]
2010-08-21 15:48 ` Linus Torvalds
2010-08-21 16:08 ` Sam Ravnborg
2010-08-23 16:34 ` Tony Luck
2010-08-22 6:57 ` Ian Campbell
2010-08-22 7:33 ` Ian Campbell
2010-08-22 9:55 ` Ian Campbell
2010-08-22 16:43 ` Linus Torvalds
2010-08-22 17:25 ` Greg KH
2010-08-22 18:21 ` Linus Torvalds
2010-08-22 19:04 ` Greg KH
2010-08-23 9:22 ` Peter Zijlstra
2010-08-23 15:42 ` ijackson
2010-08-23 16:25 ` Peter Zijlstra
2010-08-23 17:18 ` Ian Jackson
2010-08-23 17:34 ` Linus Torvalds
2010-08-23 17:53 ` Peter Zijlstra
2010-08-23 17:59 ` Peter Zijlstra
2010-08-23 18:43 ` Darren Hart
2010-08-23 18:50 ` Jeremy Fitzhardinge
2010-08-23 19:07 ` Peter Zijlstra
2010-08-23 19:23 ` Jeremy Fitzhardinge
2010-08-23 19:26 ` Peter Zijlstra
2010-08-23 19:54 ` Jeremy Fitzhardinge
2010-08-24 7:08 ` Peter Zijlstra
2010-08-24 7:20 ` Peter Zijlstra
2010-08-23 19:03 ` Ian Campbell
2010-08-23 17:40 ` Peter Zijlstra
2010-08-23 18:53 ` Jeremy Fitzhardinge
2010-08-25 8:28 ` [Stable-review] " Stefan Bader
2010-08-23 9:00 ` Peter Zijlstra
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=1282391770.29609.1223.camel@localhost.localdomain \
--to=ijc@hellion.org.uk \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=stable-review@kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome