lkml.org 
[lkml]   [2004]   [Jul]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: procfs permissions on 2.6.x
On Sun, Jul 04, 2004 at 02:55:42PM -0700, Andrew Morton wrote:
>
> 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.

Why on the earth do we ever want to allow chown/chmod on procfs in the first
place?

Al, who'd missed that stuff back in 2.5.42, but would love to hear explanation
anyway.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:04    [W:0.054 / U:0.988 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site