mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pascal Schmidt <der.eremit@email.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Possible permissions bug on NFSv3 kernel client
Date: Sat, 1 May 2004 12:54:52 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0405011240420.231@neptune.local> (raw)
In-Reply-To: <1083357597.13656.37.camel@lade.trondhjem.org>

On Fri, 30 Apr 2004, Trond Myklebust wrote:

> So why do you think that is inconsistent with my statement: "the
> permissions checking has to be done by the server, period"?

I see it wasn't clear from my reply. I don't disagree at all.
Permission checking is the server's job. Clients are untrusted.

> This should be entirely consistent with local file behaviour.
> Particularly since the code to deal with the read-only mount option in
> nfs_permission() was pretty much cut-n-pasted from vfs_permission().

The original poster said it didn't work for him on an NFSv3 mount.
Looking at nfs_permission() I (of course) agree it looks innocent
enough.

-- 
Ciao,
Pascal

  reply	other threads:[~2004-05-01 10:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1QqNJ-4QH-37@gated-at.bofh.it>
     [not found] ` <1QqNJ-4QH-39@gated-at.bofh.it>
     [not found]   ` <1QqNJ-4QH-35@gated-at.bofh.it>
     [not found]     ` <1Qrhg-5hH-29@gated-at.bofh.it>
2004-04-30 20:17       ` Pascal Schmidt
2004-04-30 20:39         ` Trond Myklebust
2004-05-01 10:54           ` Pascal Schmidt [this message]
2004-05-04  9:55           ` Colin Paton
2004-05-04 13:52             ` Trond Myklebust
     [not found] <1QhAA-5zc-13@gated-at.bofh.it>
     [not found] ` <1QnPD-2pg-1@gated-at.bofh.it>
2004-04-29 20:49   ` Pascal Schmidt
2004-04-29 21:17     ` Trond Myklebust
2004-04-29 11:02 Colin Paton
2004-04-29 17:39 ` Trond Myklebust

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=Pine.LNX.4.58.0405011240420.231@neptune.local \
    --to=der.eremit@email.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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®