Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 3 Aug 2012 13:19:24 +0200
From: richard -rw- weinberger <>
To: Cyrill Gorcunov <>
Cc: Pavel Emelyanov <>, "Eric W. Biederman" <>, 
	Kees Cook <>, Thomas Gleixner <>,, 
	Randy Dunlap <>, Darren Hart <>, 
	Peter Zijlstra <>, Andrew Morton <>, 
	Jiri Kosina <>, David Howells <>, 
	"Serge E. Hallyn" <>,,,
Subject: Re: [PATCH v2] futex: mark get_robust_list as deprecated

On Fri, Aug 3, 2012 at 1:02 PM, Cyrill Gorcunov <> wrote:
>> >> I'm using this system call in an application and noticed that's marked
>> >> as deprecated now.
>> >> My application collects all kind of information from crashing programs.
>> >> It's installed in /proc/sys/kernel/core_pattern.
>> >>
>> >> If program X is crashing it executes get_robust_list(X) to get the
>> >> address of the robust list
>> >> and reads the list from /proc/X/mem.
>> >>
>> >> Is there another way to get the robust list from another program (by it's pid)?
>> >
>> > The folks doing checkpoint/restart claim to not need this, so there
>> > might be a way either that or they just haven't hit this problem yet.
>> >
>> > What you are doing sounds like a reasonable use of get_robust_list to me.
>> >
>> CRIU folks, how do you deal with futex robust lists?
> Well, I believe we were over-optimistic in claiming that we don't need this
> syscall (to be fair I think we simply yet not faced the problem Eric points).
> So we need some way to fetch this address and set it back. If get_robust_list
> get deprecated maybe we could print it out in /proc/pid/stat or something?

Kees, you said get_robust_list() can be used to bypass ASLR.
How? What makes it worse than /proc/pid/maps?

If the robust list address itself is bad, removing get_robust_list()
and putting the
information into /proc is useless.


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.