linux-kernel - Re: sysfs: duplicate filename '74' can not be created

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 3 Mar 2008 16:14:03 +0000 (GMT)
From:	Holger Kiehl <Holger.Kiehl@....de>
To:	Alexey Dobriyan <adobriyan@...il.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: sysfs: duplicate filename '74' can not be created

On Mon, 3 Mar 2008, Holger Kiehl wrote:

> On Mon, 3 Mar 2008, Alexey Dobriyan wrote:
>
>> On 3/3/08, Holger Kiehl <Holger.Kiehl@....de> wrote:
>>> I get this approx. 4 hours after booting into 2.6.24.3 (2.6.23.16 worked
>>> fine). This system has 4 CPU's (single core) and 8GB ram. Here some more
>>> details:
>>> 
>>> 
>>> Mar 3 13:36:56 helena -- MARK --
>>> Mar 3 13:50:01 helena kernel: sysfs: duplicate filename '74' can not be
>>> created
>>> Mar 3 13:50:01 helena kernel: WARNING: at fs/sysfs/dir.c:424 
>>> sysfs_add_one()
>> 
>>> Mar 3 13:54:05 helena kernel: Code: 48 8b 04 c2 49 89 04 24 55 9d 31 c0
>>> c1 eb 0f 48 85 d2 0f 95
>>> Mar 3 13:54:05 helena kernel: RIP [<ffffffff80279170>]
>>> __kmalloc_track_caller+0x85/0xb9
>>> Mar 3 13:54:05 helena kernel: RSP <ffff8101dad09da8>
>>> Mar 3 13:54:05 helena kernel: ---[ end trace b8695bfb4832866d ]---
>> 
>>> Any idea what is causing this? Kernel 2.6.23.* seems to be fine.
>> 
>> Turn CONFIG_USER_SCHED off.
>> 
> I think you mean CONFIG_FAIR_USER_SCHED?
>
>> I'll look at why oops happened.
>> 
> If it helps I can send you all the oopses. I just posted this one.
>
I forgot to mention that ALL oopses where always on CPU3.

Holger

--
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/