From: Oleg Nesterov <oleg@redhat.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>,
John Stultz <john.stultz@linaro.org>,
Tommi Rantala <tt.rantala@gmail.com>
Subject: Re: [PATCH v2] posix-cpu-timers: fix nanosleep task_struct leak
Date: Thu, 7 Feb 2013 19:37:45 +0100 [thread overview]
Message-ID: <20130207183745.GA9902@redhat.com> (raw)
In-Reply-To: <20130207160427.GA6189@redhat.com>
Thanks Stanislaw.
I think this patch is fine.
On 02/07, Stanislaw Gruszka wrote:
>
> In do_cpu_nanosleep() we do posic_cpu_timer_create(), but forgot
> corresponding posix_cpu_timer_del() what lead to task_struct leak.
>
> Reported-and-tested-by: Tommi Rantala <tt.rantala@gmail.com>
> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
> ---
> v1 -> v2: add comments
>
> kernel/posix-cpu-timers.c | 23 +++++++++++++++++++++--
> 1 file changed, 21 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/posix-cpu-timers.c b/kernel/posix-cpu-timers.c
> index a278cad..942ca27 100644
> --- a/kernel/posix-cpu-timers.c
> +++ b/kernel/posix-cpu-timers.c
> @@ -1401,8 +1401,10 @@ static int do_cpu_nanosleep(const clockid_t which_clock, int flags,
> while (!signal_pending(current)) {
> if (timer.it.cpu.expires.sched == 0) {
> /*
> - * Our timer fired and was reset.
> + * Our timer fired and was reset, below
> + * deletion can not fail.
> */
> + posix_cpu_timer_del(&timer);
> spin_unlock_irq(&timer.it_lock);
> return 0;
> }
> @@ -1420,9 +1422,26 @@ static int do_cpu_nanosleep(const clockid_t which_clock, int flags,
> * We were interrupted by a signal.
> */
> sample_to_timespec(which_clock, timer.it.cpu.expires, rqtp);
> - posix_cpu_timer_set(&timer, 0, &zero_it, it);
> + error = posix_cpu_timer_set(&timer, 0, &zero_it, it);
> + if (!error) {
> + /*
> + * Timer is now unarmed, deletion can not fail.
> + */
> + posix_cpu_timer_del(&timer);
> + }
> spin_unlock_irq(&timer.it_lock);
>
> + while (error == TIMER_RETRY) {
> + /*
> + * We need to handle case when timer was or is in the
> + * middle of firing. In other cases we already freed
> + * resources.
> + */
> + spin_lock_irq(&timer.it_lock);
> + error = posix_cpu_timer_del(&timer);
> + spin_unlock_irq(&timer.it_lock);
> + }
> +
> if ((it->it_value.tv_sec | it->it_value.tv_nsec) == 0) {
> /*
> * It actually did fire already.
> --
> 1.7.11.7
>
prev parent reply other threads:[~2013-02-07 18:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 13:39 clock_nanosleep() task_struct leak Tommi Rantala
2013-02-01 13:52 ` Thomas Gleixner
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 [this message]
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=20130207183745.GA9902@redhat.com \
--to=oleg@redhat.com \
--cc=davej@redhat.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sgruszka@redhat.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).