From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755155Ab3BDTd0 (ORCPT ); Mon, 4 Feb 2013 14:33:26 -0500 Received: from mx1.redhat.com ([209.132.183.28]:21123 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754689Ab3BDTdY (ORCPT ); Mon, 4 Feb 2013 14:33:24 -0500 Date: Mon, 4 Feb 2013 20:32:23 +0100 From: Oleg Nesterov To: Thomas Gleixner Cc: Tommi Rantala , LKML , Dave Jones , John Stultz , Stanislaw Gruszka Subject: Re: clock_nanosleep() task_struct leak Message-ID: <20130204193223.GA11910@redhat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/01, Thomas Gleixner wrote: > > 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<----- posix_cpu_timer_create()->get_task_struct() I guess... Cough. I am not sure I ever understood this code, but now it certainly looks as if I never saw it before. All I can say is: I'll try to take another look tomorrow :/ > Groan. That code probably has more than that leak burried inside. Oh. yes... but if you meant something connected to this particular "test-case" please tell us ;) Oleg.