From: Richard Weinberger <richard@nod.at>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
dvhart@linux.intel.com, paul.gortmaker@windriver.com,
jkosina@suse.cz, rob@landley.net,
Randy Dunlap <rdunlap@xenotime.net>,
"Eric W. Biederman" <ebiederm@xmission.com>,
David Howells <dhowells@redhat.com>,
"Serge E. Hallyn" <serge.hallyn@canonical.com>,
kernel-hardening@lists.openwall.com, spender@grsecurity.net,
keescook@chromium.org, tglx@linutronix.de,
Cyrill Gorcunov <gorcunov@openvz.org>,
xemul@parallels.com, stable@vger.kernel.org,
#@programming.kicks-ass.net, 3.4.x@programming.kicks-ass.net
Subject: [kernel-hardening] Re: [PATCH] Revert "futex: Mark get_robust_list as deprecated"
Date: Mon, 06 Aug 2012 16:57:09 +0200 [thread overview]
Message-ID: <501FDB45.4050104@nod.at> (raw)
In-Reply-To: <1344264832.27828.65.camel@twins>
[-- Attachment #1: Type: text/plain, Size: 507 bytes --]
Am 06.08.2012 16:53, schrieb Peter Zijlstra:
> On Fri, 2012-08-03 at 15:29 +0200, Richard Weinberger wrote:
>> get_robust_list has at least two valid use cases.
>> 1. checkpoint/restore in userspace
>> 2. post mortem analysis
>
> Shouldn't this then also be added as a comment somewhere near the
> implementation to avoid a repeat of this deprecate / undeprecate cycle?
Or someone submits a patch to glibc and the man-pages project to make this
system call official...
Thanks,
//richard
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Richard Weinberger <richard@nod.at>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
dvhart@linux.intel.com, paul.gortmaker@windriver.com,
jkosina@suse.cz, rob@landley.net,
Randy Dunlap <rdunlap@xenotime.net>,
"Eric W. Biederman" <ebiederm@xmission.com>,
David Howells <dhowells@redhat.com>,
"Serge E. Hallyn" <serge.hallyn@canonical.com>,
kernel-hardening@lists.openwall.com, spender@grsecurity.net,
keescook@chromium.org, tglx@linutronix.de,
Cyrill Gorcunov <gorcunov@openvz.org>,
xemul@parallels.com, stable@vger.kernel.org,
#@programming.kicks-ass.net, 3.4.x@programming.kicks-ass.net
Subject: Re: [PATCH] Revert "futex: Mark get_robust_list as deprecated"
Date: Mon, 06 Aug 2012 16:57:09 +0200 [thread overview]
Message-ID: <501FDB45.4050104@nod.at> (raw)
In-Reply-To: <1344264832.27828.65.camel@twins>
[-- Attachment #1: Type: text/plain, Size: 507 bytes --]
Am 06.08.2012 16:53, schrieb Peter Zijlstra:
> On Fri, 2012-08-03 at 15:29 +0200, Richard Weinberger wrote:
>> get_robust_list has at least two valid use cases.
>> 1. checkpoint/restore in userspace
>> 2. post mortem analysis
>
> Shouldn't this then also be added as a comment somewhere near the
> implementation to avoid a repeat of this deprecate / undeprecate cycle?
Or someone submits a patch to glibc and the man-pages project to make this
system call official...
Thanks,
//richard
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2012-08-06 14:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 13:29 [kernel-hardening] [PATCH] Revert "futex: Mark get_robust_list as deprecated" Richard Weinberger
2012-08-03 13:34 ` [kernel-hardening] " Cyrill Gorcunov
2012-08-03 13:34 ` Cyrill Gorcunov
2012-08-03 14:04 ` [kernel-hardening] " richard -rw- weinberger
2012-08-03 14:04 ` richard -rw- weinberger
2012-08-03 14:19 ` [kernel-hardening] " Eric W. Biederman
2012-08-03 17:17 ` Kees Cook
2012-08-03 17:17 ` Kees Cook
2012-08-06 14:53 ` [kernel-hardening] " Peter Zijlstra
2012-08-06 14:53 ` Peter Zijlstra
2012-08-06 14:57 ` Richard Weinberger [this message]
2012-08-06 14:57 ` Richard Weinberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=501FDB45.4050104@nod.at \
--to=richard@nod.at \
--cc=#@programming.kicks-ass.net \
--cc=3.4.x@programming.kicks-ass.net \
--cc=a.p.zijlstra@chello.nl \
--cc=dhowells@redhat.com \
--cc=dvhart@linux.intel.com \
--cc=ebiederm@xmission.com \
--cc=gorcunov@openvz.org \
--cc=jkosina@suse.cz \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=rdunlap@xenotime.net \
--cc=rob@landley.net \
--cc=serge.hallyn@canonical.com \
--cc=spender@grsecurity.net \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=xemul@parallels.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.