From: Matthew Wilcox <matthew@wil.cx>
To: Andrew Morton <akpm@osdl.org>
Cc: Matthew Wilcox <matthew@wil.cx>,
torvalds@osdl.org, linux-arch@vger.kernel.org, roland@redhat.com
Subject: Re: [PATCH] Remove spurious BUG from posix-cpu-timers
Date: Sat, 19 Mar 2005 04:59:20 +0000 [thread overview]
Message-ID: <20050319045920.GL21986@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20050318205334.087395d3.akpm@osdl.org>
On Fri, Mar 18, 2005 at 08:53:34PM -0800, Andrew Morton wrote:
> Matthew Wilcox <matthew@wil.cx> wrote:
> >
> >
> > PA-RISC does not necessarily have interrupts disabled while timers are
> > running. This doesn't appear to be a requirement, but posix-cpu-timers
> > seems to think it is.
> >
>
> But a bit later on we do
>
> spin_lock(&tsk->sighand->siglock);
>
> rather than spin_lock_irqsave()?
We're in interrupt context ... we're ok, unless another interrupt handler
tries to take the same spinlock. Maybe the posix cpu timer code should
be using _irqsave anyway?
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2005-03-19 4:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-19 4:45 [PATCH] Remove spurious BUG from posix-cpu-timers Matthew Wilcox
2005-03-19 4:53 ` Andrew Morton
2005-03-19 4:59 ` Matthew Wilcox [this message]
2005-03-20 7:38 ` Roland McGrath
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=20050319045920.GL21986@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=akpm@osdl.org \
--cc=linux-arch@vger.kernel.org \
--cc=roland@redhat.com \
--cc=torvalds@osdl.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