From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752747AbaEBTMw (ORCPT ); Fri, 2 May 2014 15:12:52 -0400 Received: from www.linutronix.de ([62.245.132.108]:43885 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752004AbaEBTMv (ORCPT ); Fri, 2 May 2014 15:12:51 -0400 Date: Fri, 2 May 2014 21:12:53 +0200 (CEST) From: Thomas Gleixner To: Vince Weaver cc: Peter Zijlstra , Ingo Molnar , linux-kernel@vger.kernel.org, Steven Rostedt Subject: Re: [perf] more perf_fuzzer memory corruption In-Reply-To: Message-ID: References: <20140501150948.GR11096@twins.programming.kicks-ass.net> <20140502154217.GW11096@twins.programming.kicks-ass.net> <20140502162234.GX11096@twins.programming.kicks-ass.net> <20140502172731.GK30445@twins.programming.kicks-ass.net> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2 May 2014, Vince Weaver wrote: > On Fri, 2 May 2014, Peter Zijlstra wrote: > > > On Fri, May 02, 2014 at 12:43:17PM -0400, Vince Weaver wrote: > > > On Fri, 2 May 2014, Peter Zijlstra wrote: > > > > > > > In principle the vfs file refcounting should be responsible for that. > > > > But I'll go over it in a bit. > > > > > > The poll code is ancient and the C-parser in my head really can't handle > > > it very well. > > > > Yeah, that code isn't my favourite part either.. > > > > > Anyway for completeness this is the kind of thing I'm seeing. > > > The poll() manpage isn't very clear about what is supposed to happen if > > > you poll() on a closed file descriptor. > > > > POLLNVAL > > Invalid request: fd not open (output only). > > > > Seems applicable.. > > You're right and it seems to return that properly, so having poll be > active might just be a weird co-incidence. > > > Also, could you send your entire diff this way so we're more or less > > staring at the same code again? > > that last test I ran was just 3.15-rc1 plus the last patch you sent, > plus a patch to allow -pg on the event.c file, plus an unrelated one that > works around the current make-kpkg debian breakage. Hmm, and where comes the WARN_ON in _free_event() from? That's not in Peters last patch. Thanks, tglx