From: Thomas Gleixner <tglx@linutronix.de>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@amacapital.net>,
Cyrill Gorcunov <gorcunov@openvz.org>,
Nicholas Piggin <npiggin@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/mm: Do not allow non-MAP_FIXED mapping across DEFAULT_MAP_WINDOW border
Date: Mon, 13 Nov 2017 16:43:26 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1711131642370.1851@nanos> (raw)
In-Reply-To: <20171107130539.52676-1-kirill.shutemov@linux.intel.com>
On Tue, 7 Nov 2017, Kirill A. Shutemov wrote:
> In case of 5-level paging, we don't put any mapping above 47-bit, unless
> userspace explicitly asked for it.
>
> Userspace can ask for allocation from full address space by specifying
> hint address above 47-bit.
>
> Nicholas noticed that current implementation violates this interface:
> we can get vma partly in high addresses if we ask for a mapping at very
> end of 47-bit address space.
>
> Let's make sure that, when consider hint address for non-MAP_FIXED
> mapping, start and end of resulting vma are on the same side of 47-bit
> border.
What happens for mappings with MAP_FIXED which cross the border?
Thanks,
tglx
--
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:[~2017-11-13 15:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 13:05 [PATCH] x86/mm: Do not allow non-MAP_FIXED mapping across DEFAULT_MAP_WINDOW border Kirill A. Shutemov
2017-11-13 15:43 ` Thomas Gleixner [this message]
2017-11-13 16:41 ` Kirill A. Shutemov
2017-11-13 16:57 ` Thomas Gleixner
2017-11-13 19:14 ` Thomas Gleixner
2017-11-13 20:06 ` Kirill A. Shutemov
2017-11-13 21:14 ` Thomas Gleixner
2017-11-14 12:05 ` Kirill A. Shutemov
2017-11-14 12:11 ` Thomas Gleixner
2017-11-13 20:00 ` Kirill A. Shutemov
2017-11-13 21:17 ` Thomas Gleixner
2017-11-14 12:06 ` Kirill A. Shutemov
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=alpine.DEB.2.20.1711131642370.1851@nanos \
--to=tglx@linutronix.de \
--cc=gorcunov@openvz.org \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=npiggin@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).