Re: 2.6.7-rc2-bk4: empty-named directory in /sys

[Greg KH <greg@kroah.com>]

On Fri, Jun 04, 2004 at 10:53:23PM +0300, Denis Vlasenko wrote:
> # ls /sys
>    block  bus  class  devices  firmware  module
> # ls -l /sys
> total 0
> drwxr-xr-x   9 root     root            0 Jun  5  2004
> drwxr-xr-x  29 root     root            0 Jun  5  2004 block
> drwxr-xr-x  10 root     root            0 Jun  5  2004 bus
> drwxr-xr-x  16 root     root            0 Jun  5  2004 class
> drwxr-xr-x   7 root     root            0 Jun  5  2004 devices
> drwxr-xr-x   2 root     root            0 Jun  5  2004 firmware
> drwxr-xr-x  30 root     root            0 Jun  5  2004 module
> 
> I cannot enter that directory. Actually, it looks more like
> directory named " ", because I get similar ls outputs when
> I create regular directory named " ". However, I can enter into
> regular directory named " ", unlike /sys one.
> 
> # mkdir " " a b c
> # ls
>    a  b  c
> # ls -l
> total 0
> drwxr-xr-x   2 root     root           48 Jun  4 22:45
> drwxr-xr-x   2 root     root           48 Jun  4 22:45 a
> drwxr-xr-x   2 root     root           48 Jun  4 22:45 b
> drwxr-xr-x   2 root     root           48 Jun  4 22:45 c
> 
> .config and boot messages are attached

Hm, is the hostap code in the main kernel tree now?  That's the only
thing odd that I see from your messages.  Does this happen with
2.6.7-rc2 with no extra patches?

thanks,

greg k-h