mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Mike McCormack <mikem@ring3k.org>
Cc: kosaki.motohiro@jp.fujitsu.com,
	Andrew Morton <akpm@linux-foundation.org>,
	oleg@redhat.com, serue@us.ibm.com, jmorris@namei.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc: Add complete process group list
Date: Thu, 24 Jun 2010 11:41:38 +0900 (JST)	[thread overview]
Message-ID: <20100624110836.B5B2.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <4C221F0E.8070502@ring3k.org>

> * modify kernel to list all groups in /proc/<pid>/status 
>     - very long lines become possible in status file
>     - no way to know whether you're using an old kernel with 32 group limit
>        or new kernel and pid only has 32 groups

Is this necessary? Why?
Who need 32 groups limitation?


> * modify kernel to add /proc/<pid>/groups
>     - more kernel-userland interface

My personal opinion (aka my personal prefer) is,
 - If fixing /proc/<pid>/status is zero downside, it should do.
 - If fixing /proc/</pid>status is some downside (e.g. performance down),
   /proc/<pid>groups is better

because, 99% user don't use >32groups.


And, personally I dislike following three ;)

> * implement LOCAL_CREDS for unix domain sockets in Linux
>     - work
> 
> * limit number of groups to 32
>     - limit is imposed by /proc code
> 
> * create multiple unix domian sockets per privilege with group r/w only
>     - seems like trouble




  reply	other threads:[~2010-06-24  2:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22 15:07 Mike McCormack
2010-06-22 16:04 ` Oleg Nesterov
2010-06-22 22:37 ` Andrew Morton
2010-06-23 14:49   ` Mike McCormack
2010-06-24  2:41     ` KOSAKI Motohiro [this message]
2010-06-23  0:10 ` KOSAKI Motohiro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100624110836.B5B2.A69D9226@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikem@ring3k.org \
    --cc=oleg@redhat.com \
    --cc=serue@us.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®