LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Frank Mayhar <fmayhar@google.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Roland McGrath <roland@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Alexey Dobriyan <adobriyan@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Oleg Nesterov <oleg@tv-sign.ru>
Subject: Re: [PATCH 2.6.27-rc5 incremental re-resubmit] Fix itimer/many thread hang.
Date: Tue, 30 Sep 2008 08:33:13 +0200 [thread overview]
Message-ID: <20080930063313.GA23690@elte.hu> (raw)
In-Reply-To: <1222291416.30299.6.camel@bobble.smo.corp.google.com>
* Frank Mayhar <fmayhar@google.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
next prev parent reply other threads:[~2008-09-30 6:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 16:54 [PATCH 2.6.27-rc5 resubmit] " Frank Mayhar
2008-09-12 20:27 ` Andrew Morton
2008-09-14 15:06 ` Ingo Molnar
2008-09-14 15:07 ` [PATCH] timers: fix itimer/many thread hang, fix Ingo Molnar
2008-09-14 15:09 ` [PATCH 2.6.27-rc5 resubmit] Fix itimer/many thread hang Ingo Molnar
2008-09-15 18:09 ` Frank Mayhar
2008-09-16 8:41 ` Ingo Molnar
2008-09-17 19:03 ` Frank Mayhar
2008-09-17 19:13 ` Roland McGrath
2008-09-17 20:12 ` Frank Mayhar
2008-09-18 10:23 ` Ingo Molnar
2008-09-18 13:50 ` Frank Mayhar
2008-09-22 20:22 ` [PATCH 2.6.27-rc5 re-resubmit] " Frank Mayhar
2008-09-23 11:40 ` Ingo Molnar
2008-09-23 12:52 ` [boot crash] " Ingo Molnar
2008-09-23 13:59 ` Oleg Nesterov
2008-09-23 16:09 ` Frank Mayhar
2008-09-23 22:56 ` Frank Mayhar
2008-09-24 21:23 ` [PATCH 2.6.27-rc5 incremental " Frank Mayhar
2008-09-27 18:08 ` Ingo Molnar
2008-09-30 6:33 ` Ingo Molnar [this message]
2008-09-30 16:36 ` Frank Mayhar
2008-10-01 16:20 ` Frank Mayhar
2008-10-02 9:43 ` Ingo Molnar
2008-09-14 15:12 ` [PATCH 2.6.27-rc5 resubmit] " Ingo Molnar
2008-09-14 15:14 ` Ingo Molnar
2008-09-14 19:31 ` Roland McGrath
2008-09-15 6:41 ` Ingo Molnar
2008-09-15 17:59 ` Frank Mayhar
2008-09-16 8:39 ` Ingo Molnar
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=20080930063313.GA23690@elte.hu \
--to=mingo@elte.hu \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=fmayhar@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=roland@redhat.com \
--cc=tglx@linutronix.de \
--subject='Re: [PATCH 2.6.27-rc5 incremental re-resubmit] Fix itimer/many thread hang.' \
/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
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).