All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Ferenc Wagner <wferi@niif.hu>, <linux-kernel@vger.kernel.org>,
	<alan@lxorguk.ukuu.org.uk>, <linux-usb@vger.kernel.org>
Subject: Re: 2.6.31-rc3: replugging USB serial converter uses new device node
Date: Thu, 23 Jul 2009 10:48:09 -0700	[thread overview]
Message-ID: <20090723104809.6d39b03b.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0907231042040.2825-100000@iolanthe.rowland.org>

On Thu, 23 Jul 2009 10:44:13 -0400 (EDT) Alan Stern <stern@rowland.harvard.edu> wrote:

> On Thu, 23 Jul 2009, Andrew Morton wrote:
> 
> > (cc linux-usb)
> > 
> > On Sat, 18 Jul 2009 22:04:57 +0200 Ferenc Wagner <wferi@niif.hu> wrote:
> > 
> > > Hi,
> > > 
> > > Since upgrading to 2.6.31-rc3 from 2.6.30, my ttyUSB device number
> > > keeps increasing on each replug.  Output of udevadm monitor:
> ...
> > > Dmesg is available at http://pastebin.com/d516e3e00.
> > 
> > Can anyone say whether this is expected behaviour?
> 
> It depends on whether a program is still holding the old device file 
> open when the replug occurs.

But this is new behaviour in 2.6.31-rcX.  Was something changed in this area?

> > Does it actually cause any observeable problems?  I expect things will
> > get ugly once it runs out of range.
> 
> The numbers will get reused after the corresponding device files are
> closed.
> 
> For further discussion, see this thread:
> 
> 	http://marc.info/?t=124828810800002&r=1&w=2
> 
> Alan Stern

  parent reply	other threads:[~2009-07-23 17:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-18 20:04 2.6.31-rc3: replugging USB serial converter uses new device node Ferenc Wagner
2009-07-21 11:38 ` Ferenc Wagner
2009-07-23  8:21 ` Andrew Morton
2009-07-23 10:25   ` Ferenc Wagner
2009-07-23 14:44   ` Alan Stern
2009-07-23 15:11     ` Kay Sievers
2009-07-23 17:48     ` Andrew Morton [this message]
2009-07-23 18:21       ` Alan Stern

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=20090723104809.6d39b03b.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=wferi@niif.hu \
    /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.