From: Andy Lutomirski <luto@amacapital.net>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Sasha Levin <sasha.levin@oracle.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Dave Jones <davej@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Pavel Emelyanov <xemul@parallels.com>
Subject: Re: mm: NULL ptr deref handling mmaping of special mappings
Date: Thu, 15 May 2014 14:42:48 -0700 [thread overview]
Message-ID: <CALCETrXe80dx+ODPF1o2iUMOEOO_JAdev4f9gOQ4SUj4JQv36Q@mail.gmail.com> (raw)
In-Reply-To: <20140515213124.GT28328@moon>
On Thu, May 15, 2014 at 2:31 PM, Cyrill Gorcunov <gorcunov@gmail.com> wrote:
> On Fri, May 16, 2014 at 12:19:14AM +0400, Cyrill Gorcunov wrote:
>>
>> I see what you mean. We're rather targeting on bare x86-64 at the moment
>> but compat mode is needed as well (not yet implemented though). I'll take
>> a precise look into this area. Thanks!
>
> Indeed, because we were not running 32bit tasks vdso32-setup.c::arch_setup_additional_pages
> has never been called. That's the mode we will have to implement one day.
>
> Looking forward the question appear -- will VDSO_PREV_PAGES and rest of variables
> be kind of immutable constants? If yes, we could calculate where the additional
> vma lives without requiring any kind of [vdso] mark in proc/pid/maps output.
Please don't!
These might, in principle, even vary between tasks on the same system.
Certainly the relative positions of the vmas will be different
between 3.15 and 3.16, since we need almost my entire cleanup series
to reliably put them into their 3.16 location. And I intend to change
the number of pages in 3.16 or 3.17.
--Andy
next prev parent reply other threads:[~2014-05-15 21:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 15:55 mm: NULL ptr deref handling mmaping of special mappings Sasha Levin
2014-05-14 20:23 ` Andrew Morton
2014-05-14 20:41 ` Sasha Levin
2014-05-14 21:03 ` Andrew Morton
2014-05-14 21:11 ` Sasha Levin
2014-05-14 21:31 ` Andrew Morton
2014-05-14 21:33 ` Andy Lutomirski
2014-05-14 22:11 ` Cyrill Gorcunov
2014-05-14 22:23 ` Andy Lutomirski
2014-05-15 2:36 ` Pavel Emelyanov
2014-05-15 19:42 ` Andy Lutomirski
2014-05-19 8:27 ` Pavel Emelyanov
2014-05-19 8:40 ` Cyrill Gorcunov
2014-05-15 8:45 ` Cyrill Gorcunov
2014-05-15 19:46 ` Andy Lutomirski
2014-05-15 19:53 ` Cyrill Gorcunov
2014-05-15 19:59 ` Andy Lutomirski
2014-05-15 20:19 ` Cyrill Gorcunov
2014-05-15 21:31 ` Cyrill Gorcunov
2014-05-15 21:42 ` Andy Lutomirski [this message]
2014-05-15 21:57 ` Cyrill Gorcunov
2014-05-15 22:15 ` Andy Lutomirski
2014-05-16 22:40 ` Andy Lutomirski
2014-05-16 22:56 ` H. Peter Anvin
2014-05-17 6:15 ` Cyrill Gorcunov
2014-05-14 22:51 ` Andy Lutomirski
2014-05-14 21:26 ` Andy Lutomirski
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=CALCETrXe80dx+ODPF1o2iUMOEOO_JAdev4f9gOQ4SUj4JQv36Q@mail.gmail.com \
--to=luto@amacapital.net \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sasha.levin@oracle.com \
--cc=xemul@parallels.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;
as well as URLs for NNTP newsgroup(s).