From: Steven Rostedt <rostedt@goodmis.org>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Roland McGrath <roland@redhat.com>, Andrew Morton <akpm@osdl.org>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: [BUG] Race condition with it_real_fn in kernel/itimer.c
Date: Thu, 16 Jun 2005 07:44:55 -0400 [thread overview]
Message-ID: <1118922295.4512.23.camel@localhost.localdomain> (raw)
In-Reply-To: <1118921624.4512.16.camel@localhost.localdomain>
On Thu, 2005-06-16 at 07:33 -0400, Steven Rostedt wrote:
> int do_setitimer(int which, struct itimerval *value, struct itimerval *ovalue)
> {
> struct task_struct *tsk = current;
> static spinlock_t lock = SPIN_LOCK_UNLOCKED;
>
> [...]
> spin_lock(&lock);
> spin_unlock(&tsk->sighand->siglock);
> del_timer_sync(&tsk->signal->real_timer);
> spin_lock(&tsk->sighand->siglock);
> spin_unlock(&lock);
OK, I just got out of bed, so I'm not too with it :-)
This is pretty much a guaranteed deadlock! So the first spin_lock needs
to go before the siglock. That should do it!
case ITIMER_REAL:
spin_lock_irq(&lock);
spin_lock(&tsk->sighand->siglock);
[...]
spin_unlock(&tsk->sighand->siglock);
del_timer_sync(&tsk->signal->real_timer);
spin_lock(&tsk->sighand->siglock);
spin_unlock(&lock);
We just need to keep two do_setitimer calls from grabbing the siglock.
That first string of code didn't prevent that.
-- Steve
next prev parent reply other threads:[~2005-06-16 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 17:39 [BUG] Race condition with it_real_fn in kernel/itimer.c Oleg Nesterov
2005-06-15 18:37 ` Steven Rostedt
2005-06-15 19:34 ` [PATCH] " Steven Rostedt
2005-06-16 7:44 ` Oleg Nesterov
2005-06-16 11:33 ` Steven Rostedt
2005-06-16 11:44 ` Steven Rostedt [this message]
2005-06-16 14:30 ` [PATCH] Re: [BUG] Race condition with it_real_fn inkernel/itimer.c Oleg Nesterov
2005-06-16 9:03 ` [BUG] Race condition with it_real_fn in kernel/itimer.c 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=1118922295.4512.23.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--cc=roland@redhat.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