From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: Nick Piggin <npiggin@suse.de>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Hugh Dickins <hugh@veritas.com>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [patch][rfc] mm: have expand_stack honour VM_LOCKED
Date: Fri, 17 Oct 2008 08:50:41 -0400 [thread overview]
Message-ID: <1224247841.1736.24.camel@lts-notebook> (raw)
In-Reply-To: <20081017093701.GA14409@wotan.suse.de>
On Fri, 2008-10-17 at 11:37 +0200, Nick Piggin wrote:
> On Fri, Oct 17, 2008 at 06:32:07PM +0900, KOSAKI Motohiro wrote:
> > > > Hi Nick,
> > > >
> > > > > Is this valid?
> > > > >
> > > > >
> > > > > It appears that direct callers of expand_stack may not properly lock the newly
> > > > > expanded stack if they don't call make_pages_present (page fault handlers do
> > > > > this).
> > > >
> > > > When happend this issue?
> > > >
> > > > I think...
> > > >
> > > > case 1. explit mlock to stack
> > > >
> > > > 1. mlock to stack
> > > > -> make_pages_present is called via mlock(2).
> > > > 2. stack increased
> > > > -> no page fault happened.
> > > >
> > > > case 2. swapout and mlock stack
> > > >
> > > > 1. stack swap out
> > > > 2. mlock to stack
> > > > -> the page doesn't swap in at the time.
> > > > 3. page fault in the stack
> > > > -> the page swap in
> > > > (no need make_present_page())
> > > >
> > > >
> > > > So, it seems this patch isn't necessary.
> > >
> > > What if you you page fault the stack further than a single page down?
> > >
> >
> > I see. thanks.
> >
> > But unfortunately, this patch conflicted against unevictable patch series.
> > I'll make for -mm version patch few days after if you don't like do that.
>
> Well, it's not a big deal. I just wanted to get some comments to see whether
> the patch seems to be valid. Let's wait and see what gets merged in this
> window, then I'll resubmit this patch unless anybody sees a problem with it.
>
> Thanks for looking at it,
Hmmm. guess I should drain my inbox--not to mention a couple more cups
of coffee--before responding...
Lee
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-10-17 12:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 5:01 Nick Piggin
2008-10-17 5:41 ` KOSAKI Motohiro
2008-10-17 9:08 ` Nick Piggin
2008-10-17 9:32 ` KOSAKI Motohiro
2008-10-17 9:33 ` KOSAKI Motohiro
2008-10-17 9:37 ` Nick Piggin
2008-10-17 12:50 ` Lee Schermerhorn [this message]
2008-10-17 12:48 ` Lee Schermerhorn
2008-10-17 13:42 ` Hugh Dickins
2008-10-17 13:55 ` Nick Piggin
2008-10-17 15:06 ` Hugh Dickins
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=1224247841.1736.24.camel@lts-notebook \
--to=lee.schermerhorn@hp.com \
--cc=hugh@veritas.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
/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