From: Andy Lutomirski <luto@amacapital.net>
To: Andy Lutomirski <luto@kernel.org>,
Oleg Nesterov <oleg@redhat.com>,
Kees Cook <keescook@chromium.org>
Cc: X86 ML <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH v2 0/6] mm, x86/vdso: Special IO mapping improvements
Date: Tue, 29 Dec 2015 05:12:49 -0800 [thread overview]
Message-ID: <CALCETrWLrKtNAajEwOHV2dO8K8oPoMN+Fvyc3XwuAa+ofFewxQ@mail.gmail.com> (raw)
In-Reply-To: <CALCETrUo4U9RwOVBZu7P0d9DjtgRTFOyUQFteoVQroMdaOwVuQ@mail.gmail.com>
On Wed, Dec 23, 2015 at 3:56 PM, Andy Lutomirski <luto@amacapital.net> wrote:
> Hi Oleg and Kees-
>
> I meant to cc you on this in the first place, but I failed. If you
> have a few minutes, want to take a peek at these and see if you can
> poke any holes in them? I'm reasonably confident that they're a
> considerable improvement over the old state of affairs, but they might
> still not be perfect.
>
> Let me know if you want me to email out a fresh copy. This series
> applies to tip:x86/asm.
Hi -tip people:
please don't apply this series. It has a race. I'll send v3.
--Andy
>
> --Andy
>
> On Mon, Dec 14, 2015 at 10:31 AM, Andy Lutomirski <luto@kernel.org> wrote:
>> This applies on top of the earlier vdso pvclock series I sent out.
>> Once that lands in -tip, this will apply to -tip.
>>
>> This series cleans up the hack that is our vvar mapping. We currently
>> initialize the vvar mapping as a special mapping vma backed by nothing
>> whatsoever and then we abuse remap_pfn_range to populate it.
>>
>> This cheats the mm core, probably breaks under various evil madvise
>> workloads, and prevents handling faults in more interesting ways.
>>
>> To clean it up, this series:
>>
>> - Adds a special mapping .fault operation
>> - Adds a vm_insert_pfn_prot helper
>> - Uses the new .fault infrastructure in x86's vdso and vvar mappings
>> - Hardens the HPET mapping, mitigating an HW attack surface that bothers me
>>
>> akpm, can you ack patck 1?
>>
>> Changes from v1:
>> - Lots of changelog clarification requested by akpm
>> - Minor tweaks to style and comments in the first two patches
>>
>> Andy Lutomirski (6):
>> mm: Add a vm_special_mapping .fault method
>> mm: Add vm_insert_pfn_prot
>> x86/vdso: Track each mm's loaded vdso image as well as its base
>> x86,vdso: Use .fault for the vdso text mapping
>> x86,vdso: Use .fault instead of remap_pfn_range for the vvar mapping
>> x86/vdso: Disallow vvar access to vclock IO for never-used vclocks
>>
>> arch/x86/entry/vdso/vdso2c.h | 7 --
>> arch/x86/entry/vdso/vma.c | 124 ++++++++++++++++++++------------
>> arch/x86/entry/vsyscall/vsyscall_gtod.c | 9 ++-
>> arch/x86/include/asm/clocksource.h | 9 +--
>> arch/x86/include/asm/mmu.h | 3 +-
>> arch/x86/include/asm/vdso.h | 3 -
>> arch/x86/include/asm/vgtod.h | 6 ++
>> include/linux/mm.h | 2 +
>> include/linux/mm_types.h | 22 +++++-
>> mm/memory.c | 25 ++++++-
>> mm/mmap.c | 13 ++--
>> 11 files changed, 151 insertions(+), 72 deletions(-)
>>
>> --
>> 2.5.0
>>
>
>
>
> --
> Andy Lutomirski
> AMA Capital Management, LLC
--
Andy Lutomirski
AMA Capital Management, LLC
--
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>
prev parent reply other threads:[~2015-12-29 13:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 18:31 Andy Lutomirski
2015-12-14 18:31 ` [PATCH v2 1/6] mm: Add a vm_special_mapping .fault method Andy Lutomirski
2015-12-14 18:31 ` [PATCH v2 2/6] mm: Add vm_insert_pfn_prot Andy Lutomirski
2015-12-14 18:31 ` [PATCH v2 3/6] x86/vdso: Track each mm's loaded vdso image as well as its base Andy Lutomirski
2015-12-14 18:31 ` [PATCH v2 4/6] x86,vdso: Use .fault for the vdso text mapping Andy Lutomirski
2015-12-14 18:31 ` [PATCH v2 5/6] x86,vdso: Use .fault instead of remap_pfn_range for the vvar mapping Andy Lutomirski
2015-12-14 18:31 ` [PATCH v2 6/6] x86/vdso: Disallow vvar access to vclock IO for never-used vclocks Andy Lutomirski
2015-12-23 23:56 ` [PATCH v2 0/6] mm, x86/vdso: Special IO mapping improvements Andy Lutomirski
2015-12-29 13:12 ` Andy Lutomirski [this message]
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=CALCETrWLrKtNAajEwOHV2dO8K8oPoMN+Fvyc3XwuAa+ofFewxQ@mail.gmail.com \
--to=luto@amacapital.net \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=oleg@redhat.com \
--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