Re: [PATCH 0/9] Devices accessibility control group (v4)

[Greg KH]

On Wed, Mar 05, 2008 at 08:23:35PM +0300, Pavel Emelyanov wrote:
> Changes from v3:
> * Ported on 2.6.25-rc3-mm1;
> * Re-splitted into smaller pieces;
> * Added more comments to tricky places.
> 
> This controller allows to tune the devices accessibility by tasks,
> i.e. grant full access for /dev/null, /dev/zero etc, grant read-only
> access to IDE devices and completely hide SCSI disks.

 From within the kernel itself?  The kernel should not be keeping track
of the mode of devices, that's what the filesystem holding /dev is for.
Those modes change all the time depending on the device plugged in, and
the user using the "console".  Why should the kernel need to worry about
any of this?

> Tasks still can call mknod to create device files, regardless of
> whether the particular device is visible or accessible, but they
> may not be able to open it later.
> 
> This one hides under CONFIG_CGROUP_DEVS option.
> 
> To play with it - run a standard procedure:
> 
>  # mount -t container none /cont/devs -o devices
>  # mkdir /cont/devs/0
>  # echo -n $$ > /cont/devs/0/tasks

What is /cont/ for?

> and tune device permissions.

How is this done?

Why would the kernel care about this stuff?

confused,

greg k-h
--
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/