From: Ingo Molnar <mingo@elte.hu>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] rtc: lockdep fix
Date: Wed, 20 Sep 2006 10:47:28 +0200 [thread overview]
Message-ID: <20060920084728.GA17887@elte.hu> (raw)
In-Reply-To: <4511008E.5090005@linux.intel.com>
* Arjan van de Ven <arjan@linux.intel.com> wrote:
> >ouch! That is a scenario that could lead to real lockups. Fix looks
> >good and necessary for v2.6.18 to me.
>
> btw this entire code path is evil; the rtc_get_rtc_time() function can
> do really long delays which is unsuitable for being called in
> interrupt context!
yeah - but i dont think it triggers that often, and a fix for that
probably isnt for v2.6.18.
Ingo
prev parent reply other threads:[~2006-09-20 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 19:54 [PATCH] rtc: lockdep fix/workaround Peter Zijlstra
2006-09-20 8:21 ` [PATCH] rtc: lockdep fix Ingo Molnar
2006-09-20 8:49 ` Arjan van de Ven
2006-09-20 8:47 ` Ingo Molnar [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=20060920084728.GA17887@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
/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