mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Tommi Rantala <tt.rantala@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@redhat.com>,
	John Stultz <john.stultz@linaro.org>,
	Oleg Nesterov <oleg@redhat.com>
Subject: Re: clock_nanosleep() task_struct leak
Date: Fri, 1 Feb 2013 14:52:07 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.02.1302011450160.11905@ionos> (raw)
In-Reply-To: <CA+ydwtqUUAR9zf3dp+N1JRW+if88EZ73i+5BQtuggVPDFVdCBg@mail.gmail.com>

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 <time.h>
> 
> 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

  reply	other threads:[~2013-02-01 13:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 13:39 Tommi Rantala
2013-02-01 13:52 ` Thomas Gleixner [this message]
2013-02-04 19:32   ` Oleg Nesterov
2013-02-05 10:34     ` Stanislaw Gruszka
2013-02-05 10:55       ` Thomas Gleixner
2013-02-06 11:23         ` Stanislaw Gruszka
2013-02-06 12:01           ` Tommi Rantala
2013-02-06 15:15             ` [PATCH] posix-cpu-timers: fix nanosleep " Stanislaw Gruszka
2013-02-06 16:10               ` Oleg Nesterov
2013-02-07 12:22                 ` Stanislaw Gruszka
2013-02-07 13:24                   ` Oleg Nesterov
2013-02-07 16:04                     ` [PATCH v2] " Stanislaw Gruszka
2013-02-07 18:37                       ` Oleg Nesterov

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=alpine.LFD.2.02.1302011450160.11905@ionos \
    --to=tglx@linutronix.de \
    --cc=davej@redhat.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=tt.rantala@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome