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: Fri, 21 Jul 2006 00:11:06 +0200 [thread overview]
Message-ID: <20060720221106.GA5062@janus> (raw)
In-Reply-To: <44BFEA4C.6050602@wetafx.co.nz>
On Fri, Jul 21, 2006 at 08:40:44AM +1200, Bill Ryder wrote:
[...]
> This phrase is worrying:
>
> When there is no group id information passed downwards
> then it reverts to old behavior too.
>
> Why would no group id information be passed?
There are a few NFS operations (or related ones such as
for file locking) which do not need that information IIRC.
"old behavior" means doing what it does _today_.
> For someone of my level of knowledge of the kernel the README does not
> convince me it will work in all situations.
NFS with AUTH_UNIX authentication cannot possibly get worse than it is
today with respect to processes in more than 16 groups. And the patch
is effectively disabled for processes in <=16 groups so I wouldn't
worry.
Anyway, a revised patch from you which no longer sorts the first 16
groups for compatibility reasons is probably easier to get merged.
--
Frank
prev parent reply other threads:[~2006-07-20 22:11 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
2006-07-20 20:40 ` Bill Ryder
2006-07-20 22:11 ` Frank van Maarseveen [this message]
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=20060720221106.GA5062@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.