From: Greg KH <greg@kroah.com>
To: David Miller <davem@davemloft.net>
Cc: jens.axboe@oracle.com, kay.sievers@vrfy.org, rjw@sisk.pl,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
htejun@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: linux-2.6.23-git3: Many sysfs-related warnings in dmesg
Date: Tue, 16 Oct 2007 16:23:50 -0700 [thread overview]
Message-ID: <20071016232350.GB24827@kroah.com> (raw)
In-Reply-To: <20071016.153248.95506316.davem@davemloft.net>
On Tue, Oct 16, 2007 at 03:32:48PM -0700, David Miller wrote:
> From: Greg KH <greg@kroah.com>
> Date: Tue, 16 Oct 2007 14:37:30 -0700
>
> > Kay, are we doing something wrong in userspace when renaming wireless
> > devices such that we can overlap names?
>
> It does it for all network devices, I see this ugly message on every
> single system I have from Fedora foo to RHEL foo to ubuntu foo to
> debian foo.
>
> udev simply applies the MAC address to device name rules blindly, it
> doesn't check if the device already has the desired name already
Ugh :(
> It's been like this forever, and since userland has been doing it for
> so long, you can't warn on this there is too much established
> practice. Expecting people to install "fixed" udev is not an
> acceptable answer, the warning is a regression and therefore you'll
> have to remove the kernel warning for this case and live with this
> issue essentially forever.
Nope, I guess we will have to take out the check (or put it under the
kobject debugging flag), unless Kay has any other ideas...
thanks,
greg k-h
next prev parent reply other threads:[~2007-10-16 23:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-13 19:26 Rafael J. Wysocki
2007-10-16 4:50 ` Greg KH
2007-10-16 20:04 ` Rafael J. Wysocki
2007-10-16 20:42 ` Greg KH
2007-10-16 20:50 ` Jens Axboe
2007-10-16 21:13 ` Rafael J. Wysocki
2007-10-16 21:36 ` Greg KH
2007-10-16 23:58 ` Rafael J. Wysocki
2007-10-17 10:17 ` Kay Sievers
2007-10-17 17:35 ` Rafael J. Wysocki
2007-10-16 21:37 ` Greg KH
2007-10-16 22:32 ` David Miller
2007-10-16 23:23 ` Greg KH [this message]
2007-10-17 10:16 ` Kay Sievers
2007-10-24 23:43 ` Greg KH
2007-10-24 23:52 ` Greg KH
2007-10-25 16:58 ` Kay Sievers
2007-10-17 10:22 ` Kay Sievers
2007-10-17 10:33 ` Jens Axboe
2007-10-17 10:44 ` Jens Axboe
2007-10-16 20:49 ` Jens Axboe
2007-10-26 17:05 Larry Finger
2007-10-26 18:07 ` Kay Sievers
2007-10-26 18:20 ` Larry Finger
2007-10-27 2:36 ` Greg KH
2007-10-27 6:08 ` Kay Sievers
2007-10-27 6:32 ` 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=20071016232350.GB24827@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=htejun@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.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
Powered by JetHome