Re: [PATCH] add file position info to proc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> On Fri, 2007-03-09 at 10:23 -0500, Benjamin LaHaise wrote:
> > On Fri, Mar 09, 2007 at 09:15:06AM -0600, Dave Kleikamp wrote:
> > > I think this information would be a little easier to access if there
> > > would be a single file per pid or thread containing something like:
> > > 
> > > handle	flags	pos	path
> > > 0	0100002	1234	/dev/pts/1
> > > 1	0100004	5678	/tmp/output
> > > etc.
> > 
> > That would not be a good idea, as not all users have the same permissions 
> > for viewing this information.
> 
> How will this have different permission issues than Miklos' patch?
> 
> > It's also quite against the design philosophy 
> > used elsewhere in /proc.
> 
> What's so different between this and /proc/<pid>/maps
> or /proc/<pid>/mounts?

I think the problem is not with permissions, but with scaling to large
numbers of file descriptors.

The user is usually interested in a single file descriptor, so it
would be a large waste of resources to put together all this info at
the kernel end, just to let the user parse it all and select the
single line in which s/he is interested in.

Miklos
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux