All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: J <jhnlmn@yahoo.com>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: Possible race condition in usb-serial.c
Date: Wed, 20 Dec 2006 12:43:54 -0800	[thread overview]
Message-ID: <20061220204354.GA4039@kroah.com> (raw)
In-Reply-To: <20061220193231.39261.qmail@web32911.mail.mud.yahoo.com>

On Wed, Dec 20, 2006 at 11:32:31AM -0800, J wrote:
> Thank you for the explanation.
> 
> > serial_close is safe because serial_disconnect
> > lowers the refcount
> 
> Sorry, I meant serial_open, as in my original example.
> 
> I am currently trying to fix a legacy 2.4 based USB
> driver and I am having various races, 
> serial_open/usb_serial_disconnect is the most lively.
> I am not asking your help in fixing this old 2.4 junk
> (in fact I already fixed it using a global semaphore
> to protect serial_table).

Which usb-serial driver are you having problems with?  What is the oops
trace?  What version of the 2.4 kernel are you using?

And why are you taking the linux-usb-devel list out of the cc:?  :)

thanks,

greg k-h

  parent reply	other threads:[~2006-12-20 20:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-19 19:21 Possible race condition in usb-serial.c J
2006-12-19 20:15 ` Oliver Neukum
2006-12-19 22:33   ` J
2006-12-20  9:47     ` Oliver Neukum
2006-12-20 15:10       ` [linux-usb-devel] " Alan Stern
2006-12-20 21:02         ` Oliver Neukum
2006-12-20 19:32       ` J
2006-12-20 20:43         ` Oliver Neukum
2006-12-20 22:24           ` J
2006-12-22 18:14             ` Oliver Neukum
2006-12-22 19:08               ` J
2006-12-22 19:59                 ` Oliver Neukum
2006-12-22 20:51                   ` J
2006-12-20 20:43         ` Greg KH [this message]
2006-12-20 22:39           ` J
2006-12-20 22:52             ` 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=20061220204354.GA4039@kroah.com \
    --to=greg@kroah.com \
    --cc=jhnlmn@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.