From: Philip Lawatsch <philip@lawatsch.at>
To: Philip Lawatsch <philip@lawatsch.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFSv3 / VFS and group problems
Date: Tue, 24 Jan 2006 13:01:22 +0100 [thread overview]
Message-ID: <43D61712.9080300@lawatsch.at> (raw)
In-Reply-To: <43D55DC3.9080900@lawatsch.at>
Philip Lawatsch wrote:
> Hi,
>
> I've had the joy to debug a production system with a really crappy setup.
>
> They have a user "fred" which belongs to ~5000 groups (say
> group1-group5000).
>
>
> So far so bad. Even worse, they have a nfs backend with lots of files
> which are owned by users belonging to these groups.
>
> Ok, now my problem is that "fred" can open a file which is
>
> -rw-rw---- someone group300 foo
>
> but a read on this file will fail with EIO
>
> Since group300 is way beyond the 16 groups nfs supports shouldn't fred
> actually get a EACCES back from the open call?
>
> Problem happens with 2.6.13 (vanilla, not tainted) on both server and
> client.
Just tried it between two 2.6.15.1 machines. It works as expected there.
Seems that the client actually screwed around with the machines more
than he was willing to admit. Sorry for the noise.
kind regards Philip
prev parent reply other threads:[~2006-01-24 12:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 22:50 Philip Lawatsch
2006-01-24 12:01 ` Philip Lawatsch [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=43D61712.9080300@lawatsch.at \
--to=philip@lawatsch.at \
--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
all inboxes | Powered by JetHome®