From: Holger Kiehl <Holger.Kiehl@dwd.de>
To: Greg KH <gregkh@suse.de>
Cc: Dhaval Giani <dhaval@linux.vnet.ibm.com>,
Alexey Dobriyan <adobriyan@sw.ru>,
linux-kernel <linux-kernel@vger.kernel.org>,
vatsa@linux.vnet.ibm.com, mingo@elte.hu
Subject: Re: sysfs: duplicate filename '74' can not be created
Date: Fri, 7 Mar 2008 07:32:21 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0803070728290.22139@diagnostix.dwd.de> (raw)
In-Reply-To: <20080304192435.GA5525@suse.de>
On Tue, 4 Mar 2008, Greg KH wrote:
> On Tue, Mar 04, 2008 at 10:03:39PM +0530, Dhaval Giani wrote:
>> On Tue, Mar 04, 2008 at 07:09:40PM +0300, Alexey Dobriyan wrote:
>>> [Cc'ing /sys/kernel/uids guys]
>>>
>>
>> [Also adding gregkh to the cc :)]
>>
>>>> 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:50:01 helena kernel: Pid: 21911, comm: sshd Not tainted 2.6.24.3 #1
>
> What kernel version is this? 2.6.24 had lots of "issues" with the uids
> code, I'm amazed it worked at all :)
>
If that is so, would it not be better to disable this code in the stable
branch, at least don't set it as default? Or maybe mark this as experimental?
Holger
next prev parent reply other threads:[~2008-03-07 7:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 16:09 Alexey Dobriyan
2008-03-04 16:33 ` Dhaval Giani
2008-03-04 19:24 ` Greg KH
2008-03-05 8:59 ` Dhaval Giani
2008-03-06 6:00 ` Greg KH
2008-03-06 9:15 ` Alexey Dobriyan
2008-03-07 7:32 ` Holger Kiehl [this message]
2008-03-07 7:24 ` Holger Kiehl
2008-03-07 7:56 ` Holger Kiehl
2008-03-13 7:33 ` Holger Kiehl
-- strict thread matches above, loose matches on Subject: below --
2008-03-03 14:58 Holger Kiehl
2008-03-03 15:50 ` Alexey Dobriyan
2008-03-03 16:05 ` Holger Kiehl
2008-03-03 16:14 ` Holger Kiehl
2008-03-03 16:17 ` Alexey Dobriyan
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=Pine.LNX.4.64.0803070728290.22139@diagnostix.dwd.de \
--to=holger.kiehl@dwd.de \
--cc=adobriyan@sw.ru \
--cc=dhaval@linux.vnet.ibm.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vatsa@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®