linux-kernel - Re: [GIT pull] x86 vdso updates

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BANLkTi=y2vGbj_LMqyXzj4JPL+w_KL+=yQ@mail.gmail.com>
Date:	Sun, 29 May 2011 10:59:11 -0400
From:	Andrew Lutomirski <luto@....edu>
To:	Mikael Pettersson <mikpe@...uu.se>
Cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>, x86@...nel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [GIT pull] x86 vdso updates

On Sun, May 29, 2011 at 10:39 AM, Mikael Pettersson <mikpe@...uu.se> wrote:
> Ingo Molnar writes:
>  >
>  > * Andrew Lutomirski <luto@....edu> wrote:
>  >
>  > > On Fri, May 27, 2011 at 7:36 AM, Andrew Lutomirski <luto@....edu> wrote:
>  > > > 3. Add int 0xcc and use it from vgettimeofday.  It will SIGSEGV if
>  > > > called from a user address (so it has no risk of ever becoming ABI)
>  > > > and it will do gettimeofday if called from the right address.  (I like
> ...
>  > > Make it a real syscall but with extra constraints.  It would have the
>  > > same calling convention as the syscall instruction, but it would turn
>  > > into SIGKILL if the calling address isn't in the VSYSCALL page
>
> This will make things difficult for user-space dynamic binary instrumentation
> applications, since these normally execute generated code at different
> addresses than the original code.
>
> Is there a safe fallback for this particular vsyscall?

All of the vsyscalls have vDSO versions that work like any other code.

Alternatively, if the dynamic instrumentation code knew about
vsyscalls, it could just not instrument addresses in the vsyscall
page.

What existing applications would get broken?

--Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/