Linux NFS development
 help / color / mirror / Atom feed
From: Wei Yongjun <yjwei@cn.fujitsu.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: Question: When NFS client check dir's permission, it	does not check the cache data
Date: Wed, 27 Jun 2007 13:22:03 +0800	[thread overview]
Message-ID: <4681F3FB.7040609@cn.fujitsu.com> (raw)
In-Reply-To: <1182913754.12836.61.camel@heimdal.trondhjem.org>

[-- Attachment #1: Type: text/plain, Size: 1817 bytes --]

>
>> I think code "status = nfs_access_get_cached(inode, cred, &cache);" can do
>> this. And it works.
>> Other question: why only optimize all write operations, read operations
>> are not optimized? If read options is optimized, it can do the same things,
>> do not use access to check permissions, and server will check permissions
>> when we perform the read op.
>>     
>
> Huh? What read operations are we failing to optimise and how?
>   

I mean that read a dir, such as lookup a dir.
If I reply a getattr as that dir has no lookup permission, and then do a
"cat /nfsroot/dir/file" at client, client will not send lookup procedure to
server, because client used the cache data of the dir. It like this:
client server
#ls /nfsroot
readdirplus ------------------>
<------------- readdirplus reply
(attribute of dir has no lookup permission)
# cat /nfsroot/dir/file
(send nothing, used cache data)
-------no package is send-------

If no cache data exists, it would like this:
client server
#ls /nfsroot
readdirplus ------------------>
<------------- readdirplus reply
(attribute of dir has no lookup permission)
# cat /nfsroot/dir/file
access(dir) ------------------->
<------------- access reply(dir)
(has no lookup permission)

And if has permission to lookup dir, it would like this:
client server
#ls /nfsroot
readdirplus ------------------>
<------------- readdirplus reply
(attribute of dir has no lookup permission)
# cat /nfsroot/dir/file
access(dir) -------------------> (*1)
<------------- access reply(dir)
lookup(file) ------------------->
<------------- lookup reply(file)
read(file) ------------------->
<------------- read reply(file)

While you optimize all write operations to omit access procedure, can
this access (*1) be omitted? Then lookup(file) will return NOPERM.

Regards
Wei Yongjun




[-- Attachment #2: Type: text/plain, Size: 286 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

[-- Attachment #3: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-06-27  5:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25  8:52 Question: When NFS client check dir's permission, it does not check the cache data Wei Yongjun
2007-06-25 18:09 ` Muntz, Daniel
2007-06-25 20:08 ` Trond Myklebust
2007-06-27  1:24   ` Wei Yongjun
2007-06-27  3:09     ` Trond Myklebust
2007-06-27  5:22       ` Wei Yongjun [this message]
2007-06-27 14:25         ` Trond Myklebust
2007-06-28  3:06           ` Wei Yongjun
2007-07-26  5:12             ` Wei Yongjun
2007-07-26 16:26               ` 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=4681F3FB.7040609@cn.fujitsu.com \
    --to=yjwei@cn.fujitsu.com \
    --cc=nfs@lists.sourceforge.net \
    --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