>
>I think that's the problem. A socket isn't a file-system and the
>code won't set either bits if it isn't. Perhaps, the kernel code
>needs to consider a socket as a virtual file of some kind?
I think they are a virtual file of some kind:
[root@mason ~]# ls -l /proc/4361/fd
lrwx------ 1 root root 64 May 12 12:35 3 -> socket:[41460]
lr-x------ 1 root root 64 May 12 12:35 4 -> pipe:[41496]
l-wx------ 1 root root 64 May 12 12:35 5 -> pipe:[41496]
These "files" (socket:[] and pipe:[]) have a dentry in sockfs and
pipefs (you can't mount the fss, but they are there, see /proc/filesystems)
Jan Engelhardt
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
