linux-kernel - Re: [PATCH] x86_64: fix perms/range of vsyscall vma in /proc/*/maps

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: <200611100607.45391.ak@suse.de>
Date:	Fri, 10 Nov 2006 06:07:45 +0100
From:	Andi Kleen <ak@...e.de>
To:	Ernie Petrides <petrides@...hat.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86_64: fix perms/range of vsyscall vma in /proc/*/maps

On Friday 10 November 2006 02:20, Ernie Petrides wrote:
> Hi, Andy.  The final line of /proc/<pid>/maps on x86_64 for native 64-bit
> tasks shows an incorrect ending address and incorrect permissions.  There
> is only a single page mapped in this vsyscall region, and it is accessible
> for both read and execute.

The range reported is how much address space is reserved, but you're
right it is less.

But I don't like hardcoding a page here -- this will likely be extended
soon. Can you please create a new define VSYSCALL_REAL_LENGTH or similar 
in vsyscall.h and use that?

Thanks,
-Andi

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