[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFLxGvwnEC7O3Lf6PcU5qQO1H4NFeSRCWiy-u3mxmHCcPq==1A@mail.gmail.com>
Date: Fri, 3 Aug 2012 15:00:30 +0200
From: richard -rw- weinberger <richard.weinberger@...il.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Pavel Emelyanov <xemul@...allels.com>, Cyrill Gorcunov <gorcunov@...nvz.org>,
Kees Cook <keescook@...omium.org>, Thomas Gleixner <tglx@...utronix.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Randy Dunlap <rdunlap@...otime.net>,
Darren Hart <dvhart@...ux.intel.com>, Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Andrew Morton <akpm@...ux-foundation.org>, Jiri Kosina <jkosina@...e.cz>,
David Howells <dhowells@...hat.com>, "Serge E. Hallyn" <serge.hallyn@...onical.com>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>,
"spender@...ecurity.net" <spender@...ecurity.net>
Subject: Re: [PATCH v2] futex: mark get_robust_list as deprecated
On Fri, Aug 3, 2012 at 2:58 PM, Eric W. Biederman <ebiederm@...ssion.com> wrote:
> The permissions on the syscall were fixed them withR ptrace_may_access.
>
> We have identified two legitimate use cases.
>
> It looks like it is time for someone to generate the path to remove the depreciation.
>
> Who is up for writing and testing that patch?
I'll send a patch.
--
Thanks,
//richard
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.
