From: Greg KH <greg@kroah.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Tejun Heo <htejun@gmail.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-2.6.23-git3: Many sysfs-related warnings in dmesg
Date: Tue, 16 Oct 2007 13:42:38 -0700 [thread overview]
Message-ID: <20071016204238.GA1093@kroah.com> (raw)
In-Reply-To: <200710162204.51961.rjw@sisk.pl>
On Tue, Oct 16, 2007 at 10:04:51PM +0200, Rafael J. Wysocki wrote:
> On Tuesday, 16 October 2007 06:50, Greg KH wrote:
> > On Sat, Oct 13, 2007 at 09:26:32PM +0200, Rafael J. Wysocki wrote:
> > > Hi,
> > >
> > > There are many traces like this in my dmesg from 2.6.23-git3 (they don't
> > > appear for vanilla 2.6.23):
> > >
> > > <4>sysfs: duplicate filename 'ethxx1' can not be created
> > > WARNING: at /home/rafael/src/linux-2.6/fs/sysfs/dir.c:425 sysfs_add_one()
> > >
> > > Call Trace:
> > > [<ffffffff802d1532>] sysfs_add_one+0x5c/0xc9
> > > [<ffffffff802d2411>] sysfs_create_link+0xd1/0x12c
> > > [<ffffffff803756da>] device_rename+0x17a/0x1db
> > > [<ffffffff803c903d>] dev_change_name+0x114/0x20c
> > > [<ffffffff803c9339>] dev_ifsioc+0x204/0x2d0
> > > [<ffffffff803c9925>] dev_ioctl+0x520/0x633
> > > [<ffffffff803bf445>] sk_alloc+0x37/0x10c
> > > [<ffffffff8024b977>] up_read+0x9/0xb
> > > [<ffffffff803bc65e>] sock_ioctl+0x1fe/0x20c
> > > [<ffffffff8029b34a>] do_ioctl+0x2a/0x77
> > > [<ffffffff8029b5e8>] vfs_ioctl+0x251/0x26e
> > > [<ffffffff8029b664>] sys_ioctl+0x5f/0x83
> > > [<ffffffff8020bd4e>] system_call+0x7e/0x83
> > >
> > > net ethxx1: device_rename: sysfs_create_symlink failed (-17)
> > > sysfs: duplicate filename 'eth1' can not be created
> > >
> > > Everything seems to work, but this just looks fishy.
> >
> > This is a userspace program renaming your network device to a name that
> > is already in use. What distro and release is this?
>
> openSUSE 10.2, with some updates (not the most recent, though).
Can you try 10.3? I think we fixed this issue there.
thanks,
greg k-h
next prev parent reply other threads:[~2007-10-16 20:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-13 19:26 linux-2.6.23-git3: Many sysfs-related warnings in dmesg 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 [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
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=20071016204238.GA1093@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=htejun@gmail.com \
--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