linux-kernel - Re: [PATCH] Reading the VDSO area

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: <469CF2BC.3000306@goop.org>
Date:	Tue, 17 Jul 2007 09:47:56 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	john.blackwood@...r.com
CC:	linux-kernel@...r.kernel.org,
	Jeremy Fitzhardinge <jeremy@...source.com>,
	Andi Kleen <ak@...e.de>, Roland McGrath <roland@...hat.com>,
	bugsy@...r.com, Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] Reading the VDSO area - i386

John Blackwood wrote:
> I was doing some tests that attempt to read the VDSO area of a
> task through either the /proc/pid/mem or ptrace(PTRACE_PEEKTEXT,
> ...) interfaces, and it seems that when the CONFIG_COMPAT_VDSO kernel
> parameter is enabled, we can no longer successfully read the VDSO area
> on i386 kernels.

Thanks.  Someone else noticed this recently, and posted a near-identical
patch.  But I can't seem to find it right now...

Andrew, Andi: do you remember something like this passing by?

    J
-
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/