From: Greg KH <greg@kroah.com>
To: Nix <nix@esperi.org.uk>
Cc: linux-kernel@vger.kernel.org, Peter Osterlund <petero2@telia.com>
Subject: Re: pktcdvd -> sysfs warning with 2.6.27
Date: Sun, 12 Oct 2008 11:17:00 -0700 [thread overview]
Message-ID: <20081012181700.GA21072@kroah.com> (raw)
In-Reply-To: <87vdvyngni.fsf@hades.wkstn.nix>
On Sun, Oct 12, 2008 at 01:26:25PM +0100, Nix wrote:
> At the very end of my startup scripts, I say
>
> pktsetup cdrw /dev/cdrw
>
> to get the stuff in /etc/pktcdvd set up right.
>
> As of 2.6.27 this has started complaining:
>
> pktcdvd: writer pktcdvd0 mapped to hde
> ------------[ cut here ]------------
> WARNING: at fs/sysfs/dir.c:463 sysfs_add_one+0x2f/0x3b()
> sysfs: duplicate filename '254:0' can not be created
> Modules linked in:
> Pid: 1306, comm: pktsetup Not tainted 2.6.27-dirty #1
> [<c011ac1c>] warn_slowpath+0x50/0x71
> [<c0245c17>] ? ida_get_new_above+0xdc/0x17d
> [<c0245a8a>] ? idr_get_empty_slot+0x142/0x1f3
> [<c0245c17>] ? ida_get_new_above+0xdc/0x17d
> [<c01a1738>] ? sysfs_ilookup_test+0x0/0x16
> [<c01a1919>] ? sysfs_find_dirent+0x1b/0x2c
> [<c01a1aba>] sysfs_add_one+0x2f/0x3b
> [<c01a26f6>] sysfs_do_create_link+0xb1/0x106
> [<c01a276b>] sysfs_create_link+0xf/0x14
> [<c02749d2>] device_add+0x134/0x455
> [<c0274d0a>] device_register+0x17/0x1a
> [<c0274d8d>] device_create_vargs+0x80/0xa3
> [<c0274dd0>] device_create+0x20/0x24
> [<c028208f>] pkt_setup_dev+0x2ed/0x429
> [<c0282251>] pkt_ctl_ioctl+0x86/0x18c
> [<c0170c09>] vfs_ioctl+0x55/0x6e
> [<c0185801>] ? block_truncate_page+0xa9/0x1e0
> [<c0170e58>] do_vfs_ioctl+0x236/0x249
> [<c0170e9c>] sys_ioctl+0x31/0x4d
> [<c0102c8d>] sysenter_do_call+0x12/0x25
> [<c0185801>] ? block_truncate_page+0xa9/0x1e0
> =======================
> ---[ end trace 1cdd10ab78ee5bc6 ]---
>
> For the life of me I can't see where pkt_sysfs_dev_new() is being called
> more than once: indeed, from the trace above GCC has inlined it into
> pkt_setup_dev() as a static function called from only one place...
Perhaps some other kernel code is registering with that same major/minor
number, making it already present in sysfs. Where does that sysfs file
link to before you load your driver?
thanks,
greg k-h
next prev parent reply other threads:[~2008-10-12 18:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 12:26 pktcdvd -> sysfs warning with 2.6.27 Nix
2008-10-12 18:17 ` Greg KH [this message]
2008-10-12 20:25 ` Nix
2008-10-12 22:18 ` Greg KH
2008-10-12 22:36 ` Nix
2008-10-13 10:27 ` Philip Martin
2008-10-13 21:28 ` Nix
2008-10-13 21:47 ` Greg KH
2008-10-13 22:01 ` Alessandro Zummo
2008-10-13 22:03 ` Nix
2008-10-14 5:27 ` Peter Osterlund
2008-10-14 8:38 ` Kay Sievers
2008-10-14 9:20 ` Kay Sievers
2008-10-14 19:53 ` Peter Osterlund
2008-10-14 22:32 ` Kay Sievers
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=20081012181700.GA21072@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nix@esperi.org.uk \
--cc=petero2@telia.com \
/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.