linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kinglong Mee <kinglongmee@gmail.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: linux-nfs@vger.kernel.org, "J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: [PATCH] NFS: add FATTR4_WORD1_MODE flags for cache_consistency_bitmask
Date: Mon, 14 Apr 2014 20:59:34 +0800	[thread overview]
Message-ID: <534BDBB6.5030306@gmail.com> (raw)
In-Reply-To: <1397402659.6306.5.camel@leira.trondhjem.org>



于 2014/4/13 23:24, Trond Myklebust 写道:
> On Sun, 2014-04-13 at 22:53 +0800, Kinglong Mee wrote:
>>
>> 于 2014/4/13 22:28, Trond Myklebust 写道:
>>>
>>> On Apr 13, 2014, at 9:11, Kinglong Mee <kinglongmee@gmail.com> wrote:
>>>
>>>> After writing data at NFS client, file's access mode is inconsistent
>>>> with server.
>>>> Because WRITE proceduce changes the S_ISUID and S_ISGID bits,
>>>> but client don't get it.
>>>>
>>>> #touch hello; chmod 06777 hello; stat hello;
>>>>    File: ‘hello’
>>>>    Size: 0               Blocks: 0          IO Block: 262144 regular
>>>> empty file
>>>> Device: 24h/36d Inode: 786434      Links: 1
>>>> Access: (6777/-rwsrwsrwx)  Uid: (    0/    root)   Gid: (    0/    root)
>>>> Context: system_u:object_r:nfs_t:s0
>>>> Access: 2014-04-13 21:00:44.996908708 +0800
>>>> Modify: 2014-04-13 21:00:44.996908708 +0800
>>>> Change: 2014-04-13 21:00:45.033908705 +0800
>>>> Birth: -
>>>>
>>>> #echo 12324 > hello; stat hello; stat /nfstest/hello
>>>>    File: ‘hello’
>>>>    Size: 6               Blocks: 0          IO Block: 262144 regular file
>>>> Device: 24h/36d Inode: 786434      Links: 1
>>>> Access: (6777/-rwsrwsrwx)  Uid: (    0/    root)   Gid: (    0/    root)
>>>>           ^^^^^ it should be 0777
>>>> Context: system_u:object_r:nfs_t:s0
>>>> Access: 2014-04-13 21:00:44.996908708 +0800
>>>> Modify: 2014-04-13 21:00:45.061908703 +0800
>>>> Change: 2014-04-13 21:00:45.061908703 +0800
>>>> Birth: -
>>>>    File: ‘/nfstest/hello’
>>>>    Size: 6               Blocks: 8          IO Block: 4096   regular file
>>>> Device: 803h/2051d      Inode: 786434      Links: 1
>>>> Access: (0777/-rwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
>>>>           ^^^^^ bits on the server
>>>> Context: system_u:object_r:default_t:s0
>>>> Access: 2014-04-13 21:00:44.996908708 +0800
>>>> Modify: 2014-04-13 21:00:45.061908703 +0800
>>>> Change: 2014-04-13 21:00:45.061908703 +0800
>>>> Birth: -
>>>>
> <snip>
>>>
>>> Instead of requesting a new attribute on each and every operation just in order to deal with an extremely rare corner case, is there any reason why we can’t just do this by checking should_remove_suid(), clearing the mode bits ourselves, and then marking the attributes for revalidation?
>>
> <snip>
>> IMO, client shoulds get all metadatas from server, so, adds the flag.
>> I think should_remove_suid() should be called by nfsd, not NFS client
>
> I agree with 50% of that statement. Please see below.
>
> 8<---------------------------------------------------------------------
>>From a7b05fc5fcb433e8cfca577c9275f2012b523ee8 Mon Sep 17 00:00:00 2001
> From: Trond Myklebust <trond.myklebust@primarydata.com>
> Date: Sun, 13 Apr 2014 11:11:31 -0400
> Subject: [PATCH] NFS: Don't ignore suid/sgid bit changes after a successful
>   write
>
> If we suspect that the server may have cleared the suid/sgid bit,
> then mark the inode for revalidation.

When testing with this patch, should_remove_suid() always return false
at client, but return true at NFS server.

So that, NFS server clears the suid/sgid bit, but client also remains.

thanks,
Kinglong Mee

>
> Reported-by: Kinglong Mee <kinglongmee@gmail.com>
> Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
> ---
>   fs/nfs/write.c | 11 +++++++++--
>   1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/fs/nfs/write.c b/fs/nfs/write.c
> index 9a3b6a4cd6b9..80b03e064a09 100644
> --- a/fs/nfs/write.c
> +++ b/fs/nfs/write.c
> @@ -1401,9 +1401,16 @@ void nfs_writeback_done(struct rpc_task *task, struct nfs_write_data *data)
>   		}
>   	}
>   #endif
> -	if (task->tk_status < 0)
> +	if (task->tk_status < 0) {
>   		nfs_set_pgio_error(data->header, task->tk_status, argp->offset);
> -	else if (resp->count < argp->count) {
> +		return;
> +	}
> +
> +	/* Deal with the suid/sgid bit corner case */
> +	if (should_remove_suid(argp->context->dentry))
> +		nfs_mark_for_revalidate(inode);
> +

> +	if (resp->count < argp->count) {
>   		static unsigned long    complain;
>
>   		/* This a short write! */
>

  reply	other threads:[~2014-04-14 13:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-13 13:11 [PATCH] NFS: add FATTR4_WORD1_MODE flags for cache_consistency_bitmask Kinglong Mee
2014-04-13 14:28 ` Trond Myklebust
2014-04-13 14:53   ` Kinglong Mee
2014-04-13 15:24     ` Trond Myklebust
2014-04-14 12:59       ` Kinglong Mee [this message]
2014-04-14 13:12         ` Trond Myklebust
2014-04-14 13:31           ` Kinglong Mee
2014-04-14 15:00             ` Trond Myklebust
2014-04-15  5:02               ` Kinglong Mee
2014-04-15 13:22                 ` Trond Myklebust
2014-04-15 14:24                   ` Trond Myklebust
2014-04-16  2:50                     ` Kinglong Mee

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=534BDBB6.5030306@gmail.com \
    --to=kinglongmee@gmail.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.com \
    /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;
as well as URLs for NNTP newsgroup(s).