From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Tony Luck <tony.luck@gmail.com>,
Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>,
Fenghua Yu <fenghua.yu@intel.com>,
Hugh Dickins <hughd@google.com>,
linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org,
Michel Lespinasse <walken@google.com>,
Oleg Nesterov <oleg@redhat.com>,
linux-ia64@vger.kernel.org
Subject: Re: [PATCH] Don't mlock guardpage if the stack is growing up
Date: Tue, 10 May 2011 04:12:53 +0000 [thread overview]
Message-ID: <1305000773.4865.62.camel@mulgrave.site> (raw)
In-Reply-To: <BANLkTikUyUpa9-ZZBquHW4xSCEj8W8TgnA@mail.gmail.com>
On Mon, 2011-05-09 at 16:25 -0700, Linus Torvalds wrote:
> On Mon, May 9, 2011 at 4:17 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > Ok, I'll consider it tested. I'll commit it with Mikulas as author,
> > but note that I edited it so he won't get the blame if there's some
> > problem.
>
> Oh, and I marked it for stable too, although I don't know if any
> distribution really cares about parisc or ia64. And I'm not sure that
> ia64 even saw the lvm2 failure case - I'd have expected to hear about
> it if it actually happens there.
Well, it's a done deal, but here's the proof on parisc too:
Before:
c0266000-c0289000 rwxp 00000000 00:00 0 [stack]
c0266000-c0a66000 rwxp 00000000 00:00 0 [stack]
After:
bffee000-c0010000 rwxp 00000000 00:00 0 [stack]
bffee000-c0010000 rwxp 00000000 00:00 0 [stack]
James
next prev parent reply other threads:[~2011-05-10 4:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.00.1105082045250.15552@artax.karlin.mff.cuni.cz>
[not found] ` <alpine.LSU.2.00.1105081303540.16151@sister.anvils>
[not found] ` <alpine.DEB.2.00.1105091307570.32299@artax.karlin.mff.cuni.cz>
[not found] ` <BANLkTinCUQSjjif3op3H_9HDm5Eu-o+Luw@mail.gmail.com>
2011-05-09 22:07 ` [PATCH] Don't mlock guardpage if the stack is growing up Linus Torvalds
2011-05-09 22:19 ` James Bottomley
2011-05-09 22:31 ` Linus Torvalds
2011-05-09 22:53 ` Tony Luck
2011-05-09 22:58 ` Linus Torvalds
2011-05-09 23:08 ` Tony Luck
2011-05-09 23:17 ` Linus Torvalds
2011-05-09 23:25 ` Linus Torvalds
2011-05-10 4:12 ` James Bottomley [this message]
2011-05-09 22:26 ` Mikulas Patocka
2011-05-15 22:18 ` Mikulas Patocka
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=1305000773.4865.62.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=fenghua.yu@intel.com \
--cc=hughd@google.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=mikulas@artax.karlin.mff.cuni.cz \
--cc=oleg@redhat.com \
--cc=tony.luck@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=walken@google.com \
/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