From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Josh Boyer <jwboyer@gmail.com>
Cc: Kees Cook <keescook@chromium.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@xenotime.net>,
Darren Hart <dvhart@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jiri Kosina <jkosina@suse.cz>,
"Eric W. Biederman" <ebiederm@xmission.com>,
David Howells <dhowells@redhat.com>,
"Serge E. Hallyn" <serge.hallyn@canonical.com>,
linux-doc@vger.kernel.org, kernel-hardening@lists.openwall.com,
spender@grsecurity.net
Subject: [kernel-hardening] Re: [PATCH v2] futex: mark get_robust_list as deprecated
Date: Tue, 27 Mar 2012 21:13:59 +0200 [thread overview]
Message-ID: <1332875639.16159.255.camel@twins> (raw)
In-Reply-To: <CA+5PVA5FR_QoTtNVV04VXrjOujAMFHMXF4-GnyZHLPUGnvb3zA@mail.gmail.com>
On Tue, 2012-03-27 at 14:05 -0400, Josh Boyer wrote:
>
> Do you really need WARN_ONCE? It's going to spew a backtrace if this
> is called, and that is going to cause various auto-bug reporters to file
> bugs as well.
That's a positive, right? That gives extra visibility to who and what
might possibly use this thing.
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Josh Boyer <jwboyer@gmail.com>
Cc: Kees Cook <keescook@chromium.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@xenotime.net>,
Darren Hart <dvhart@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jiri Kosina <jkosina@suse.cz>,
"Eric W. Biederman" <ebiederm@xmission.com>,
David Howells <dhowells@redhat.com>,
"Serge E. Hallyn" <serge.hallyn@canonical.com>,
linux-doc@vger.kernel.org, kernel-hardening@lists.openwall.com,
spender@grsecurity.net
Subject: Re: [PATCH v2] futex: mark get_robust_list as deprecated
Date: Tue, 27 Mar 2012 21:13:59 +0200 [thread overview]
Message-ID: <1332875639.16159.255.camel@twins> (raw)
In-Reply-To: <CA+5PVA5FR_QoTtNVV04VXrjOujAMFHMXF4-GnyZHLPUGnvb3zA@mail.gmail.com>
On Tue, 2012-03-27 at 14:05 -0400, Josh Boyer wrote:
>
> Do you really need WARN_ONCE? It's going to spew a backtrace if this
> is called, and that is going to cause various auto-bug reporters to file
> bugs as well.
That's a positive, right? That gives extra visibility to who and what
might possibly use this thing.
next prev parent reply other threads:[~2012-03-27 19:13 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 23:12 [kernel-hardening] [PATCH] futex: do not leak robust list to unprivileged process Kees Cook
2012-03-19 23:12 ` Kees Cook
2012-03-20 13:31 ` [kernel-hardening] " Serge Hallyn
2012-03-20 13:31 ` Serge Hallyn
2012-03-20 17:02 ` [kernel-hardening] " Thomas Gleixner
2012-03-20 17:02 ` Thomas Gleixner
2012-03-20 17:11 ` [kernel-hardening] " Kees Cook
2012-03-20 17:11 ` Kees Cook
2012-03-20 17:23 ` [kernel-hardening] " Ingo Molnar
2012-03-20 17:23 ` Ingo Molnar
2012-03-22 23:46 ` [kernel-hardening] " Thomas Gleixner
2012-03-22 23:46 ` Thomas Gleixner
2012-03-23 17:58 ` [kernel-hardening] [PATCH] futex: mark get_robust_list as deprecated Kees Cook
2012-03-23 17:58 ` Kees Cook
2012-03-23 18:27 ` [kernel-hardening] " Thomas Gleixner
2012-03-23 18:27 ` Thomas Gleixner
2012-03-23 19:08 ` [kernel-hardening] " Kees Cook
2012-03-23 19:08 ` Kees Cook
2012-03-23 19:08 ` [kernel-hardening] [PATCH v2] " Kees Cook
2012-03-23 19:08 ` Kees Cook
[not found] ` <20120323190855.GA27213-0X9Bc/hWBUTk6RaD4rd5nQ@public.gmane.org>
2012-03-23 22:06 ` Eric W. Biederman
2012-03-23 22:06 ` Eric W. Biederman
2012-03-23 22:06 ` [kernel-hardening] " Eric W. Biederman
[not found] ` <m1fwczvuph.fsf-+imSwln9KH6u2/kzUuoCbdi2O/JbrIOy@public.gmane.org>
2012-03-23 22:10 ` Kees Cook
2012-03-23 22:10 ` Kees Cook
2012-03-23 22:10 ` [kernel-hardening] " Kees Cook
2012-03-30 5:05 ` Matt Helsley
2012-03-30 5:05 ` Matt Helsley
2012-03-30 5:05 ` [kernel-hardening] " Matt Helsley
[not found] ` <20120330050544.GA32299-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>
2012-03-30 6:14 ` Pavel Emelyanov
2012-03-30 6:14 ` Pavel Emelyanov
2012-03-30 6:14 ` [kernel-hardening] " Pavel Emelyanov
2012-03-30 22:51 ` Gene Cooperman
2012-03-30 22:51 ` [kernel-hardening] " Gene Cooperman
2012-03-30 22:51 ` Gene Cooperman
2012-03-27 18:05 ` [kernel-hardening] " Josh Boyer
2012-03-27 18:05 ` Josh Boyer
2012-03-27 19:13 ` Peter Zijlstra [this message]
2012-03-27 19:13 ` Peter Zijlstra
2012-03-29 9:56 ` [tip:core/locking] futex: Mark " tip-bot for Kees Cook
2012-08-02 10:35 ` [kernel-hardening] Re: [PATCH v2] futex: mark " richard -rw- weinberger
2012-08-02 10:35 ` richard -rw- weinberger
2012-08-02 11:11 ` [kernel-hardening] " Eric W. Biederman
2012-08-02 11:11 ` Eric W. Biederman
2012-08-03 10:17 ` [kernel-hardening] " richard -rw- weinberger
2012-08-03 10:17 ` richard -rw- weinberger
2012-08-03 11:02 ` [kernel-hardening] " Cyrill Gorcunov
2012-08-03 11:02 ` Cyrill Gorcunov
2012-08-03 11:19 ` [kernel-hardening] " richard -rw- weinberger
2012-08-03 11:19 ` richard -rw- weinberger
2012-08-03 11:27 ` [kernel-hardening] " Cyrill Gorcunov
2012-08-03 11:27 ` Cyrill Gorcunov
2012-08-03 11:30 ` [kernel-hardening] " richard -rw- weinberger
2012-08-03 11:30 ` richard -rw- weinberger
2012-08-03 11:35 ` [kernel-hardening] " Cyrill Gorcunov
2012-08-03 11:35 ` Cyrill Gorcunov
2012-08-03 11:38 ` [kernel-hardening] " richard -rw- weinberger
2012-08-03 11:38 ` richard -rw- weinberger
2012-08-03 12:38 ` [kernel-hardening] " Pavel Emelyanov
2012-08-03 12:38 ` Pavel Emelyanov
2012-08-03 12:58 ` [kernel-hardening] " Eric W. Biederman
2012-08-03 12:58 ` Eric W. Biederman
2012-08-03 13:00 ` [kernel-hardening] " richard -rw- weinberger
2012-08-03 13:00 ` richard -rw- weinberger
2012-08-03 17:16 ` [kernel-hardening] " Kees Cook
2012-08-03 17:16 ` Kees Cook
2012-08-03 18:06 ` [kernel-hardening] [PATCH] Revert "futex: Mark get_robust_list as deprecated" Richard Weinberger
2012-03-28 18:33 ` [kernel-hardening] Re: [PATCH] futex: do not leak robust list to unprivileged process Kees Cook
2012-03-28 18:33 ` Kees Cook
2012-03-28 21:24 ` [kernel-hardening] " Thomas Gleixner
2012-03-28 21:24 ` Thomas Gleixner
2012-03-29 9:55 ` [tip:core/locking] futex: Do " tip-bot for Kees Cook
2012-06-19 1:41 ` Wanlong Gao
2012-06-19 2:24 ` Serge Hallyn
2012-06-19 2:32 ` Wanlong Gao
2012-06-19 3:13 ` Serge Hallyn
2012-06-19 3:21 ` Wanlong Gao
2012-06-19 12:23 ` Serge Hallyn
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=1332875639.16159.255.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=dvhart@linux.intel.com \
--cc=ebiederm@xmission.com \
--cc=jkosina@suse.cz \
--cc=jwboyer@gmail.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=serge.hallyn@canonical.com \
--cc=spender@grsecurity.net \
--cc=tglx@linutronix.de \
/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.