From: Ingo Molnar <mingo@elte.hu>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ryan Brown <some.nzguy@gmail.com>,
Kernel development list <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@us.ibm.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
David Brownell <david-b@pacbell.net>
Subject: Re: [patch] Real-Time Preemption, -RT-2.6.13-rc6-V0.7.53-11
Date: Wed, 17 Aug 2005 08:31:38 +0200 [thread overview]
Message-ID: <20050817063138.GA5689@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0508161247030.18302-100000@iolanthe.rowland.org>
* Alan Stern <stern@rowland.harvard.edu> wrote:
> P.S.: Another routine worth examining is async_completed() in
> drivers/usb/core/devio.c.
i've added the patch below to be on the safe side.
Ingo
Index: linux/drivers/usb/core/devio.c
===================================================================
--- linux.orig/drivers/usb/core/devio.c
+++ linux/drivers/usb/core/devio.c
@@ -274,10 +274,11 @@ static void async_completed(struct urb *
struct async *as = (struct async *)urb->context;
struct dev_state *ps = as->ps;
struct siginfo sinfo;
+ unsigned long flags;
- spin_lock(&ps->lock);
- list_move_tail(&as->asynclist, &ps->async_completed);
- spin_unlock(&ps->lock);
+ spin_lock_irqsave(&ps->lock, flags);
+ list_move_tail(&as->asynclist, &ps->async_completed);
+ spin_unlock_irqrestore(&ps->lock, flags);
if (as->signr) {
sinfo.si_signo = as->signr;
sinfo.si_errno = as->urb->status;
next prev parent reply other threads:[~2005-08-17 6:31 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 11:00 [patch] Real-Time Preemption, -RT-2.6.13-rc4-V0.7.53-01, High Resolution Timers & RCU-tasklist features Ingo Molnar
2005-08-12 3:07 ` Lee Revell
2005-08-12 3:19 ` Lee Revell
2005-08-12 7:03 ` Ingo Molnar
2005-08-12 7:48 ` Thomas Gleixner
2005-08-12 7:07 ` Ingo Molnar
2005-08-13 0:28 ` Ryan Brown
2005-08-13 0:32 ` Lee Revell
2005-08-13 0:57 ` George Anzinger
2005-08-14 2:12 ` Ingo Molnar
2005-08-15 6:29 ` Ingo Molnar
2005-08-15 23:39 ` George Anzinger
2005-08-16 6:36 ` Thomas Gleixner
2005-08-15 11:18 ` [patch] Real-Time Preemption, -RT-2.6.13-rc6-V0.7.53-11 Ingo Molnar
2005-08-15 20:35 ` Peter Zijlstra
2005-08-16 3:53 ` Ingo Molnar
2005-08-16 14:35 ` Alan Stern
2005-08-16 16:12 ` Ingo Molnar
2005-08-16 16:56 ` Alan Stern
2005-08-16 17:02 ` Ingo Molnar
2005-08-17 2:23 ` David Brownell
2005-08-17 14:10 ` Alan Stern
2005-08-17 20:51 ` David Brownell
2005-08-18 4:52 ` Ingo Molnar
2005-08-18 6:37 ` David Brownell
2005-08-18 14:43 ` Alan Stern
2005-08-22 11:07 ` Ingo Molnar
2005-08-17 6:31 ` Ingo Molnar [this message]
2005-08-16 8:41 ` 2.6.13-rc6-rt1 Ingo Molnar
2005-08-16 12:32 ` 2.6.13-rc6-rt1 Michal Schmidt
2005-08-27 1:15 ` 2.6.13-rc6-rt1 Matt Mackall
2005-08-29 22:36 ` 2.6.13-rc6-rt1 Esben Nielsen
2005-08-17 0:53 ` [patch] KGDB for Real-Time Preemption systems George Anzinger
2005-08-17 6:53 ` Ingo Molnar
2005-08-17 19:16 ` George Anzinger
2005-09-05 12:23 ` Serge Noiraud
2005-09-08 0:37 ` George Anzinger
2005-09-07 8:55 ` Serge Noiraud
2005-09-07 21:16 ` George Anzinger
2005-09-08 8:57 ` Serge Noiraud
2005-09-08 20:47 ` George Anzinger
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=20050817063138.GA5689@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=david-b@pacbell.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@us.ibm.com \
--cc=some.nzguy@gmail.com \
--cc=stern@rowland.harvard.edu \
--cc=tglx@linutronix.de \
/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