From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755623Ab2C0TOW (ORCPT ); Tue, 27 Mar 2012 15:14:22 -0400 Received: from casper.infradead.org ([85.118.1.10]:56254 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753879Ab2C0TOV convert rfc822-to-8bit (ORCPT ); Tue, 27 Mar 2012 15:14:21 -0400 Message-ID: <1332875639.16159.255.camel@twins> Subject: Re: [PATCH v2] futex: mark get_robust_list as deprecated From: Peter Zijlstra To: Josh Boyer Cc: Kees Cook , Thomas Gleixner , linux-kernel@vger.kernel.org, Randy Dunlap , Darren Hart , Andrew Morton , Jiri Kosina , "Eric W. Biederman" , David Howells , "Serge E. Hallyn" , linux-doc@vger.kernel.org, kernel-hardening@lists.openwall.com, spender@grsecurity.net Date: Tue, 27 Mar 2012 21:13:59 +0200 In-Reply-To: References: <20120323190855.GA27213@www.outflux.net> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.