lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <a8e1da0710072343h2addc01eh911bdcf5c81985df@mail.gmail.com> Date: Mon, 8 Oct 2007 14:43:12 +0800 From: "Dave Young" <hidave.darkstar@...il.com> To: "Greg KH" <greg@...ah.com> Cc: "Andrew Morton" <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, linux-usb-devel@...ts.sourceforge.net Subject: Re: 2.6.23-rc8-mm2 On 9/29/07, Greg KH <greg@...ah.com> wrote: > On Sat, Sep 29, 2007 at 05:37:29PM +0800, Dave Young wrote: > > Hi, > > The kernel report warnings about sysfs filename duplicate under > > rc8-mm1 and rc8-mm2. > > 1. > > ----cut---- > > NET: Registered protocol family 16 > > ACPI: bus type pci registered > > PCI: PCI BIOS revision 2.10 entry at 0xfb93e, last bus=3 > > PCI: Using configuration type 1 > > Setting up standard PCI resources > > sysfs: duplicate filename 'usbcore' can not be created > > WARNING: at fs/sysfs/dir.c:433 sysfs_add_one() > > [<c010528f>] dump_trace+0x1bf/0x1d0 > > [<c0105358>] show_trace_log_lvl+0x18/0x30 > > [<c010537f>] show_trace+0xf/0x20 > > [<c01054a2>] dump_stack+0x12/0x20 > > [<c01c6680>] sysfs_add_one+0xa0/0xe0 > > [<c01c69e8>] create_dir+0x48/0xb0 > > [<c01c6a99>] sysfs_create_dir+0x29/0x50 > > [<c02501eb>] create_dir+0x1b/0x50 > > [<c02504b6>] kobject_add+0x46/0x150 > > [<c05a38a0>] kernel_param_sysfs_setup+0x50/0xb0 > > [<c05a39ee>] param_sysfs_builtin+0xee/0x130 > > [<c05a3a54>] param_sysfs_init+0x24/0x60 > > [<c0592866>] do_initcalls+0x46/0x1e0 > > [<c0592aa2>] kernel_init+0x62/0xb0 > > [<c0104fb3>] kernel_thread_helper+0x7/0x14 > > ======================= > > kobject_add failed for usbcore with -EEXIST, don't try to register > > things with the same name in the same directory. > > That is very wierd, do you have both USB built in and as a module > somehow? > > > [<c010528f>] dump_trace+0x1bf/0x1d0 > > [<c0105358>] show_trace_log_lvl+0x18/0x30 > > [<c010537f>] show_trace+0xf/0x20 > > [<c01054a2>] dump_stack+0x12/0x20 > > [<c0250566>] kobject_add+0xf6/0x150 > > [<c05a38a0>] kernel_param_sysfs_setup+0x50/0xb0 > > [<c05a39ee>] param_sysfs_builtin+0xee/0x130 > > [<c05a3a54>] param_sysfs_init+0x24/0x60 > > [<c0592866>] do_initcalls+0x46/0x1e0 > > [<c0592aa2>] kernel_init+0x62/0xb0 > > [<c0104fb3>] kernel_thread_helper+0x7/0x14 > > ======================= > > Module 'usbcore' failed to be added to sysfs, error number -17 > > I think I need to clean up the double stack trace here, that's reall not > needed :) > Hi, I debugged the problem, found that it is a bug of kernel/params.c, I will send a patch later to fix it. Regards dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists