Re: [1/1][PATCH] nproc v2: netlink access to /proc information

Roger Luethi
2004-09-09T18:48:28Z

On Wed, 08 Sep 2004 17:35:29 -0700, William Lee Irwin III wrote:
> On Wed, Sep 08, 2004 at 08:41:30PM +0200, Roger Luethi wrote:
> > A few notes:
> > - Access control can be implemented easily. Right now it would be bloat,
> > though -- the vast majority of fields in /proc are world-readable
> > (/proc/pid/environ being the notable exception).
> > - Additional process selectors (e.g. select by UID) are not hard to
> > add, either, should there ever be a need.
> > - There are a few things I'm not sure about: For instance, what is a good
> > return value for mm_struct related fields wrt kernel threads? I picked
> > 0, but ~(0) might be preferable because it's distinct.
> > Signed-off-by: Roger Luethi <rl@hellgate.ch>
>
> Any chance you could convert these to use the new vm statistics
> accounting?

Mea culpa. I copied the routines wholesale from 2.6.7 when I started
work on nproc. They still seemed to work with 2.6.9-rc1-bk13, I hadn't
noticed the work that had gone into field computation already. So for
CONFIG_MMU, values in both __task_mem and __task_mem_cheap are cheap
now. The routines can be merged.

!CONFIG_MMU is a different story. Presumably, it needs a change in the
fields that are offered (cp. task_mem in fs/proc/task_nommu.c).

FWIW, my prefered solution would be to have only one routine task_mem
to fill the respective struct for nproc and /proc.

There seems to be a discrepancy between current task_mem in
fs/proc/task_nommu.c and the __task_mem{,_cheap} routines you wrote
for the nproc !CONFIG_MMU case. Can you explain?

Roger