From: Ed Tomlinson <edt@aei.ca>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: sedat.dilek@gmail.com, Greg KH <gregkh@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
penberg@kernel.org, arthur@psw.ro, wylda@volny.cz
Subject: Re: Linux 2.6.35.2
Date: Sat, 14 Aug 2010 15:47:08 -0400 [thread overview]
Message-ID: <201008141547.08722.edt@aei.ca> (raw)
In-Reply-To: <AANLkTingwMvoVm_J6cmm_K3=G9rCYwOrQ=-5vK_wzGcX@mail.gmail.com>
On Saturday 14 August 2010 14:47:45 Linus Torvalds wrote:
> On Sat, Aug 14, 2010 at 11:27 AM, Ed Tomlinson <edt@aei.ca> wrote:
> >
> > It seems to be helping here. Without it 35.2 would either stall in boot or give lots of tracebacks. With it things
> > start normally and my background stuff works as expected.
>
> Ok, thanks. I've committed it to the -git tree.
>
> Just to verify: you have CONFIG_HIGHPTE enabled on a x86-32 kernel,
> right? I'd have expected this to not ever show up anywhere else, and
> I'm just verifying that there isn't anything else going on. I'm
> appending the commit message, the patch hasn't changed.
No. I have a x86-64 based kernel (amd64).
Ed
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Sat Aug 14 11:44:56 2010 -0700
>
> mm: fix page table unmap for stack guard page properly
>
> We do in fact need to unmap the page table _before_ doing the whole
> stack guard page logic, because if it is needed (mainly 32-bit x86 with
> PAE and CONFIG_HIGHPTE, but other architectures may use it too) then it
> will do a kmap_atomic/kunmap_atomic.
>
> And those kmaps will create an atomic region that we cannot do
> allocations in. However, the whole stack expand code will need to do
> anon_vma_prepare() and vma_lock_anon_vma() and they cannot do that in an
> atomic region.
>
> Now, a better model might actually be to do the anon_vma_prepare() when
> _creating_ a VM_GROWSDOWN segment, and not have to worry about any of
> this at page fault time. But in the meantime, this is the
> straightforward fix for the issue.
>
> See https://bugzilla.kernel.org/show_bug.cgi?id=16588 for details.
>
> Reported-by: Wylda <wylda@volny.cz>
> Reported-by: Sedat Dilek <sedat.dilek@gmail.com>
> Reported-by: Mike Pagano <mpagano@gentoo.org>
> Reported-by: François Valenduc <francois.valenduc@tvcablenet.be>
> Tested-by: Ed Tomlinson <edt@aei.ca>
> Cc: Pekka Enberg <penberg@kernel.org>
> Cc: Greg KH <gregkh@suse.de>
> Cc: stable@kernel.org
> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
>
> mm/memory.c | 13 ++++++-------
> 1 files changed, 6 insertions(+), 7 deletions(-)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
next prev parent reply other threads:[~2010-08-14 19:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 12:37 Linux 2.6.35.2 Sedat Dilek
2010-08-14 17:14 ` Linus Torvalds
2010-08-14 17:27 ` Sedat Dilek
2010-08-14 17:31 ` Linus Torvalds
2010-08-14 18:27 ` Ed Tomlinson
2010-08-14 18:47 ` Linus Torvalds
2010-08-14 19:01 ` wylda
2010-08-14 19:01 ` Sedat Dilek
2010-08-14 19:47 ` Ed Tomlinson [this message]
2010-08-14 21:56 ` Linus Torvalds
2010-08-14 23:39 ` Ed Tomlinson
2010-08-14 20:34 ` Sedat Dilek
-- strict thread matches above, loose matches on Subject: below --
2010-08-13 21:23 Greg KH
2010-08-13 21:23 ` Greg KH
2010-08-14 6:53 ` Heinz Diehl
2010-08-14 13:40 ` Greg KH
2010-08-14 10:35 ` Arthur Titeica
2010-08-14 11:21 ` Pekka Enberg
2010-08-14 13:39 ` Greg KH
2010-08-14 14:08 ` Arthur Titeica
2010-08-14 15:10 ` Bjarke Istrup Pedersen
2010-08-14 16:56 ` Heiko Carstens
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=201008141547.08722.edt@aei.ca \
--to=edt@aei.ca \
--cc=arthur@psw.ro \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=wylda@volny.cz \
/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