From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756669Ab3BANwM (ORCPT ); Fri, 1 Feb 2013 08:52:12 -0500 Received: from www.linutronix.de ([62.245.132.108]:34155 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754869Ab3BANwJ (ORCPT ); Fri, 1 Feb 2013 08:52:09 -0500 Date: Fri, 1 Feb 2013 14:52:07 +0100 (CET) From: Thomas Gleixner To: Tommi Rantala cc: LKML , Dave Jones , John Stultz , Oleg Nesterov Subject: Re: clock_nanosleep() task_struct leak In-Reply-To: Message-ID: References: User-Agent: Alpine 2.02 (LFD 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 B1;2601;0cOn Fri, 1 Feb 2013, Tommi Rantala wrote: > Hello, > > Trinity discovered a task_struct leak with clock_nanosleep(), reproducible with: > > -----8<-----8<-----8<----- > #include > > static const struct timespec req; > > int main(void) { > return clock_nanosleep(CLOCK_PROCESS_CPUTIME_ID, > TIMER_ABSTIME, &req, NULL); > } > -----8<-----8<-----8<----- Groan. That code probably has more than that leak burried inside. Thanks, tglx