[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080930063313.GA23690@elte.hu>
Date: Tue, 30 Sep 2008 08:33:13 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Frank Mayhar <fmayhar@...gle.com>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
Roland McGrath <roland@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Alexey Dobriyan <adobriyan@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Oleg Nesterov <oleg@...sign.ru>
Subject: Re: [PATCH 2.6.27-rc5 incremental re-resubmit] Fix itimer/many
thread hang.
* Frank Mayhar <fmayhar@...gle.com> wrote:
> /*
> * Return any ns on the sched_clock that have not yet been banked in
> * @p in case that task is currently running.
> - *
> - * Called with task_rq_lock() held on @rq.
> */
> -static unsigned long long task_delta_exec(struct task_struct *p, struct rq *rq)
> +unsigned long long task_delta_exec(struct task_struct *p)
> {
> + struct rq *rq;
> + unsigned long flags;
> + u64 ns = 0;
> +
> if (task_current(rq, p)) {
> u64 delta_exec;
hmmm ... where do we get 'rq' from?
in v3 you did this:
- rq = task_rq_lock(p, &flags);
which removed the deadlock but left us with a random uninitialized rq
variable ...
the right solution for the bug would have been to unlock it.
Miraculously we didnt actually crash anywhere visibly, found it by
reviewing the code. I thought this code gets excercised quite
frequently. The commit below fixes it.
Could you please functionality-test latest tip/master:
http://people.redhat.com/mingo/tip.git/README
with your testcase that excercises these codepaths heavily?
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists