[lkml]   [2004]   [Jul]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: procfs permissions on 2.6.x
    Hash: SHA1 wrote:
    | 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
    | place?

    Well perhaps I am on the wrong track but eg /proc/bus/usb/002/005 is my
    digital camera and unless its either world rw or owned by me (user) I
    can't get any pictures unless I make myself root.

    So yes, I would want to have chown/chmod in procfs ...

    - --
    Clemens Schwaighofer - IT Engineer & System Administration
    TEQUILA\Japan, 6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN
    Tel: +81-(0)3-3545-7703 Fax: +81-(0)3-3545-7343
    Version: GnuPG v1.2.4 (GNU/Linux)

    -----END PGP SIGNATURE-----
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:04    [W:0.020 / U:15.484 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site