From: Oleg Nesterov <oleg@redhat.com>
To: Doug Chapman <doug.chapman@hp.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
adobriyan@gmail.com, Peter Zijlstra <peterz@infradead.org>,
Roland McGrath <roland@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] account_group_exec_runtime: fix the racy usage of ->signal
Date: Fri, 7 Nov 2008 19:42:05 +0100 [thread overview]
Message-ID: <20081107184205.GA30523@redhat.com> (raw)
In-Reply-To: <1226077087.6451.18.camel@oberon>
On 11/07, Doug Chapman wrote:
>
> On Fri, 2008-11-07 at 17:21 +0100, Ingo Molnar wrote:
> > * Oleg Nesterov <oleg@redhat.com> wrote:
> >
> > > @@ -351,10 +351,12 @@ static inline void account_group_exec_ru
> > > unsigned long long ns)
> > > {
> > > struct signal_struct *sig;
> > > + unsigned long flags;
> > >
> > > - sig = tsk->signal;
> > > - if (unlikely(!sig))
> > > + if (unlikely(!lock_task_sighand(tsk, &flags)))
> > > return;
> >
> > i think this will lock up: the signal lock must not nest inside the rq
> > lock, and these accounting functions are called from within the
> > scheduler.
>
> I can confirm that this does hang on bootup.
Thanks a lot Doug.
If only I could understand what happens. I am running the 2.6.27 kernel
with the patch below just fine.
Ingo, could you please explain?
OK, perhaps we can check ->exit_state... I'll return on Monday.
--- linux-2.6.27/kernel/sched_fair.c~DBG 2008-10-10 00:13:53.000000000 +0200
+++ linux-2.6.27/kernel/sched_fair.c 2008-11-07 19:15:28.000000000 +0100
@@ -484,6 +484,16 @@ __update_curr(struct cfs_rq *cfs_rq, str
curr->vruntime += delta_exec_weighted;
}
+static void ttt(struct task_struct *tsk)
+{
+ unsigned long flags;
+
+ if (unlikely(!lock_task_sighand(tsk, &flags)))
+ return;
+
+ unlock_task_sighand(tsk, &flags);
+}
+
static void update_curr(struct cfs_rq *cfs_rq)
{
struct sched_entity *curr = cfs_rq->curr;
@@ -507,6 +517,7 @@ static void update_curr(struct cfs_rq *c
struct task_struct *curtask = task_of(curr);
cpuacct_charge(curtask, delta_exec);
+ ttt(curtask);
}
}
next prev parent reply other threads:[~2008-11-07 17:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 16:52 [PATCH] account_group_exec_runtime: fix the racy usage of ->signal Oleg Nesterov
2008-11-07 16:21 ` Ingo Molnar
2008-11-07 16:58 ` Doug Chapman
2008-11-07 18:42 ` Oleg Nesterov [this message]
2008-11-07 17:40 ` Oleg Nesterov
2008-11-08 9:28 ` Ingo Molnar
2008-11-10 13:04 ` Oleg Nesterov
2008-11-10 12:13 ` Peter Zijlstra
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=20081107184205.GA30523@redhat.com \
--to=oleg@redhat.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=doug.chapman@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--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