public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.14.3 - sysfs duplicated dentry bug
Date: Fri, 9 Dec 2005 09:55:55 -0800	[thread overview]
Message-ID: <20051209175555.GA9761@kroah.com> (raw)
In-Reply-To: <200512091848.42297.blaisorblade@yahoo.it>

On Fri, Dec 09, 2005 at 06:48:41PM +0100, Blaisorblade wrote:
> Q: Since when is a directory entry allowed to be duplicate?
> A: Since Linux 2.6.14!
> 
> $ uname -r
> 2.6.14.3-bs2-mroute
> 
> The only sysfs-related change is the use of a custom DSDT, which is new to 
> this kernel.

Known bug, fixed in the 2.6.15-rc kernel tree.  It was a timer
registering with the same name in two places :(

And yes, we should have more sysfs checks for stuff like this, any
patches in this area would be greatly appreciated.

thanks,

greg k-h

  reply	other threads:[~2005-12-09 17:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-09 17:48 2.6.14.3 - sysfs duplicated dentry bug Blaisorblade
2005-12-09 17:55 ` Greg KH [this message]
2005-12-23 22:25   ` Blaisorblade
2005-12-23 22:44     ` Greg KH

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=20051209175555.GA9761@kroah.com \
    --to=greg@kroah.com \
    --cc=blaisorblade@yahoo.it \
    --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