Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 09 Nov 2017 11:49:52 +1100
From: Michael Ellerman <>
To: "Tobin C. Harding" <>
Cc:, "Jason A. Donenfeld" <>, Theodore Ts'o <>, Linus Torvalds <>, Kees Cook <>, Paolo Bonzini <>, Tycho Andersen <>, "Roberts\, William C" <>, Tejun Heo <>, Jordan Glover <>, Greg KH <>, Petr Mladek <>, Joe Perches <>, Ian Campbell <>, Sergey Senozhatsky <>, Catalin Marinas <>, Will Deacon <>, Steven Rostedt <>, Chris Fries <>, Dave Weinstein <>, Daniel Micay <>, Djalal Harouni <>,, Network Development <>, David Miller <>
Subject: Re: [PATCH v4] scripts: add

"Tobin C. Harding" <> writes:

> On Wed, Nov 08, 2017 at 11:10:56PM +1100, Michael Ellerman wrote:
>> "Tobin C. Harding" <> writes:
> [snip]
> Hi Michael,
> I'm working an adding support for ppc64 to, I've
> added the kernel address regular expression that you suggested.


> I'd like to add the false positive for vsyscall addresses. Excuse my
> ignorance but does PowerPC use a constant address range for vsyscall like x86_64
> does? The ppc64 machine I have access to does not output anything for
> 	$ cat /proc/PID/tasks/PID/smaps		or
> 	$ cat /proc/PID/tasks/PID/maps

No we only have the vdso style vsyscall, which is mapped at user
addresses and is subject to ASLR, so you shouldn't need to worry about


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.