public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank van Maarseveen <frankvm@frankvm.com>
To: Bill Ryder <bryder@wetafx.co.nz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.18-rc1]  Make group sorting optional in the 2.6.x kernels
Date: Thu, 20 Jul 2006 11:35:57 +0200	[thread overview]
Message-ID: <20060720093557.GA1796@janus> (raw)
In-Reply-To: <44BE936B.3080107@wetafx.co.nz>

On Thu, Jul 20, 2006 at 08:17:47AM +1200, Bill Ryder wrote:
[...]
> As an aside Frank - can you point at a paper which provides a
> walkthrough of how your patch  works and what the caveats are?

	http://www.frankvm.com/nfs-ngroups/README

> For example
> 
> /top(0)/p1(2)/p3(2)/p4(2)/p5(6)/file1(6)
> /top(0)/p1(2)/p3(2)/p4(2)/p6(7)/file2(7)
> /top(0)/p1(2)/p3(2)/p4(2)/p7(8)/file3(6)
> /top(0)/p1(2)/p3(2)/p4(2)/p7(8)/file4(8)
> 
> And so on - where the (n) indicated the (gid) for that directory/file.
> So most of our directories are in the same group. But as you get further
> down the tree the groups start to change.
> 
> The process will belong to > 16 groups.

setgroups() require privilege. I don't understand how the above is
supposed to work for non-root users needing >16 groups. And when you're
root it is silly to play these group games for getting access.

-- 
Frank

  reply	other threads:[~2006-07-20  9:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-11  4:26 [PATCH 2.6.18-rc1] Make group sorting optional in the 2.6.x kernels Bill Ryder
2006-07-11  5:29 ` Randy.Dunlap
     [not found] ` <2c0942db0607111120h686e70x44037730a1a4c92f@mail.gmail.com>
2006-07-11 19:27   ` Ray Lee
     [not found] ` <2c0942db0607111109n14353c50wdaf144214d572ffe@mail.gmail.com>
2006-07-11 20:22   ` Bill Ryder
2006-07-19  8:02 ` Frank van Maarseveen
2006-07-19 20:17   ` Bill Ryder
2006-07-20  9:35     ` Frank van Maarseveen [this message]
2006-07-20 20:40       ` Bill Ryder
2006-07-20 22:11         ` Frank van Maarseveen

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=20060720093557.GA1796@janus \
    --to=frankvm@frankvm.com \
    --cc=bryder@wetafx.co.nz \
    --cc=linux-kernel@vger.kernel.org \
    /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