Re: procfs permissions on 2.6.x

[Andrew Morton]

viro@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx wrote:
>
> On Sat, Jul 03, 2004 at 02:35:58PM -0700, Andrew Morton wrote:
> > > Because it turns the question what permissions a procfs file has into
> > > a lottery game.  He only changes the incore inode owner and as soon as
> > > the inode is reclaimed the old ones return.
> > 
> > procfs inodes aren't reclaimable.
> 
> WTF do you mean "not reclaimable"?

Got confused.

>  They do get freed under memory pressure
> and recreated on later lookups.

Some do.  On my test box 1000-odd /proc inodes get allocated and fully
freed on each `ls -R /proc'.  65 /proc inodes are freed during `ls -lR
/proc/net'.  So maybe it isn't working completely.

But proc_notify_change() copies the inode's uid, gid and mode into the
proc_dir_entry, so they get correctly initialised when the inode is
reinstantiated, so afaict we have no bug here.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/