From: Alex Chiang <achiang@canonical.com>
To: Greg KH <gregkh@suse.de>
Cc: Eric Paris <eparis@redhat.com>,
linux-kernel@vger.kernel.org, jbarnes@virtuousgeek.org
Subject: Re: WARNING: at fs/sysfs/dir.c:451 sysfs_add_one: sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:01.0/slot'
Date: Wed, 14 Apr 2010 06:55:02 -0600 [thread overview]
Message-ID: <20100414125502.GA20755@canonical.com> (raw)
In-Reply-To: <20100414051017.GA17378@suse.de>
* Greg KH <gregkh@suse.de>:
> On Tue, Apr 13, 2010 at 07:33:34PM -0600, Alex Chiang wrote:
> > * Eric Paris <eparis@redhat.com>:
> > >
> > > I get one for 1.0, 1.1, 1.2, 2.0, 3.0, 4.0, 5.0. Below I only show the
> > > example for 1.0. Attached should be the full dmesg and config. Please
> > > let me know about any ideas, tests, questions, or things I can do to
> > > help debug the spew....
> >
> > These come from a patch I wrote, but unfortunately, I don't have
> > the time or hardware to properly debug them. :(
>
> It should be simple, for any dynamically allocated sysfs attribute, just
> call sysfs_attribute_initialize() before registering it with the sysfs
> core, and you will get rid of these messages.
Oh hm, I didn't realize that.
> If you have a pointer to your patch, I'll be glad to generate an add-on
> patch to resolve this issue.
In Jesse's linux-next branch:
commit 8b9cd07e02d69bb9e746a57fc987643d648c4b13
Author: Alex Chiang <achiang@hp.com>
Date: Mon Mar 8 10:24:29 2010 -0700
PCI: create function symlinks in /sys/bus/pci/slots/N/
Thanks Greg.
/ac
prev parent reply other threads:[~2010-04-14 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 19:08 WARNING: at fs/sysfs/dir.c:451 sysfs_add_one: sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:01.0/slot' Eric Paris
2010-04-14 1:33 ` Alex Chiang
2010-04-14 5:10 ` Greg KH
2010-04-14 12:55 ` Alex Chiang [this message]
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=20100414125502.GA20755@canonical.com \
--to=achiang@canonical.com \
--cc=eparis@redhat.com \
--cc=gregkh@suse.de \
--cc=jbarnes@virtuousgeek.org \
--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