mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <petkov@uni-muenster.de>
To: linux-kernel@vger.kernel.org
Cc: Greg KH <greg@kroah.com>
Subject: Re: [PATCH] Re: 2.6.9-rc1-mm4, visor.c, Badness in usb_unlink_urb
Date: Fri, 10 Sep 2004 20:24:31 +0200	[thread overview]
Message-ID: <200409102024.32082.petkov@uni-muenster.de> (raw)
In-Reply-To: <20040910140152.GA15589@kroah.com>

Hi Greg,
I'll be happy to tackle the other drivers. Question: Does usb_unlink_urb have 
to be replaced only for synchronious unlinking and if so, is the wrapping 
function responsible for checking the URB_ASYNC_UNLINK transfer flag? Here's 
a patch:

Signed-off-by: Borislav Petkov <petkov@uni-muenster.de>

--- linux-2.6.9-rc1-mm/drivers/usb/class/audio.c.orig 2004-09-10 20:05:17.000000000 +0200
+++ linux-2.6.9-rc1-mm/drivers/usb/class/audio.c 2004-09-10 20:23:12.000000000 +0200
@@ -635,13 +635,13 @@ static void usbin_stop(struct usb_audiod
   spin_unlock_irqrestore(&as->lock, flags);
   if (notkilled && signal_pending(current)) {
    if (i & FLG_URB0RUNNING)
-    usb_unlink_urb(u->durb[0].urb);
+    usb_kill_urb(u->durb[0].urb);
    if (i & FLG_URB1RUNNING)
-    usb_unlink_urb(u->durb[1].urb);
+    usb_kill_urb(u->durb[1].urb);
    if (i & FLG_SYNC0RUNNING)
-    usb_unlink_urb(u->surb[0].urb);
+    usb_kill_urb(u->surb[0].urb);
    if (i & FLG_SYNC1RUNNING)
-    usb_unlink_urb(u->surb[1].urb);
+    usb_kill_urb(u->surb[1].urb);
    notkilled = 0;
   }
  }
@@ -1114,13 +1114,13 @@ static void usbout_stop(struct usb_audio
   spin_unlock_irqrestore(&as->lock, flags);
   if (notkilled && signal_pending(current)) {
    if (i & FLG_URB0RUNNING)
-    usb_unlink_urb(u->durb[0].urb);
+    usb_kill_urb(u->durb[0].urb);
    if (i & FLG_URB1RUNNING)
-    usb_unlink_urb(u->durb[1].urb);
+    usb_kill_urb(u->durb[1].urb);
    if (i & FLG_SYNC0RUNNING)
-    usb_unlink_urb(u->surb[0].urb);
+    usb_kill_urb(u->surb[0].urb);
    if (i & FLG_SYNC1RUNNING)
-    usb_unlink_urb(u->surb[1].urb);
+    usb_kill_urb(u->surb[1].urb);
    notkilled = 0;
   }
  }


  reply	other threads:[~2004-09-10 18:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-10  8:26 Norbert Preining
2004-09-10  9:45 ` [PATCH 0/2] " Borislav Petkov
2004-09-10  9:48 ` [PATCH 1/2] " Borislav Petkov
2004-09-10 14:01   ` Greg KH
2004-09-10 18:24     ` Borislav Petkov [this message]
2004-09-14  7:47       ` [PATCH] " Greg KH
2004-09-10  9:50 ` [PATCH 2/2] Re: 2.6.9-rc1-mm4, sub-serial.c, " Borislav Petkov
2004-09-10 14:30 ` 2.6.9-rc1-mm4, visor.c, " Greg KH

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=200409102024.32082.petkov@uni-muenster.de \
    --to=petkov@uni-muenster.de \
    --cc=greg@kroah.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

all inboxes | Powered by JetHome®