From: Takashi Iwai <tiwai@suse.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Tvrtko Ursulin <tvrtko@ursulin.net>,
alsa-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Ooops when working with USB MIDI (2.6.33.1)
Date: Thu, 08 Apr 2010 14:22:36 +0200 [thread overview]
Message-ID: <s5haateyvzn.wl%tiwai@suse.de> (raw)
In-Reply-To: <4BBDA92B.8010505@ladisch.de>
At Thu, 08 Apr 2010 12:00:11 +0200,
Clemens Ladisch wrote:
>
> Tvrtko Ursulin wrote:
> > I had TuxGuitar running and an external USB MIDI device, which I then
> > turned off, on, and exited TuxGuitar at which point there was this oops.
> > ...
> > [321182.618342] IP: [<ffffffff81375d65>] _raw_spin_lock_irq+0x15/0x30
> > [321182.618449] [<ffffffffa01e2fca>] ? snd_usbmidi_output_drain+0x7a/0x100 [snd_usb_lib]
> > [321182.618462] [<ffffffffa01b7699>] ? snd_rawmidi_drain_output+0x119/0x180 [snd_rawmidi]
>
> I think that bug was introduced by this commit:
> http://git.kernel.org/linus/7a17daae8ed71bf3259d905a4fc48a5b424fa935
> which causes the driver to free many internal data structures when
> they might still be in use by userspace.
>
> Please try to revert it.
>
> I think a proper fix would be to free the URBs/buffers but not the
> driver's data structures.
>
> Takashi, do you remember what the original problem was?
Well, I have only a vague memory -- it's a similar scenario that some app
still accessing after disconnection. The URB can't be handled after
the disconnection is finished.
I think the patch below might fix in this case. You can try it
instead of reverting the commit above.
thanks,
Takashi
---
diff --git a/sound/usb/usbmidi.c b/sound/usb/usbmidi.c
index 2c59afd..81c8d85 100644
--- a/sound/usb/usbmidi.c
+++ b/sound/usb/usbmidi.c
@@ -986,6 +986,8 @@ static void snd_usbmidi_output_drain(struct snd_rawmidi_substream *substream)
DEFINE_WAIT(wait);
long timeout = msecs_to_jiffies(50);
+ if (ep->umidi->disconnected)
+ return;
/*
* The substream buffer is empty, but some data might still be in the
* currently active URBs, so we have to wait for those to complete.
@@ -1275,6 +1277,11 @@ void snd_usbmidi_disconnect(struct list_head* p)
snd_usbmidi_in_endpoint_delete(ep->in);
ep->in = NULL;
}
+ ep->active_urbs = 0;
+ if (ep->drain_urbs) {
+ ep->drain_urbs = 0;
+ wake_up(&ep->drain_wait);
+ }
}
del_timer_sync(&umidi->error_timer);
}
next prev parent reply other threads:[~2010-04-08 12:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 13:33 Ooops when working with USB MIDI (2.6.33.1) Tvrtko Ursulin
2010-04-08 10:00 ` Clemens Ladisch
2010-04-08 12:22 ` Takashi Iwai [this message]
2010-04-09 6:51 ` Tvrtko Ursulin
2010-04-09 7:19 ` Clemens Ladisch
2010-04-09 7:29 ` Takashi Iwai
2010-04-09 17:36 ` Tvrtko Ursulin
2010-04-11 7:04 ` Takashi Iwai
2010-05-03 12:48 ` Tvrtko Ursulin
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=s5haateyvzn.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tvrtko@ursulin.net \
/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