[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <201906251131.419D8ACB@keescook>
Date: Tue, 25 Jun 2019 13:08:07 -0700
From: Kees Cook <keescook@...omium.org>
To: Florian Weimer <fweimer@...hat.com>
Cc: linux-api@...r.kernel.org, kernel-hardening@...ts.openwall.com,
linux-x86_64@...r.kernel.org, linux-arch@...r.kernel.org,
Andy Lutomirski <luto@...nel.org>,
Carlos O'Donell <carlos@...hat.com>
Subject: Re: Detecting the availability of VSYSCALL
On Tue, Jun 25, 2019 at 05:15:27PM +0200, Florian Weimer wrote:
> Should we try mapping something at the magic address (without MAP_FIXED)
> and see if we get back a different address? Something in the auxiliary
> vector would work for us, too, but nothing seems to exists there
> unfortunately.
It seems like mmap() won't even work because it's in the high memory
area. I can't map something a page under the vsyscall page either, so I
can't distinguish it with mmap, mprotect, madvise, or msync. :(
--
Kees Cook
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
