On Apr 15, 2014, at 1:02, Kinglong Mee <kinglongmee@xxxxxxxxx> wrote: > > > 于 2014/4/14 23:00, Trond Myklebust 写道: >> On Mon, 2014-04-14 at 21:31 +0800, Kinglong Mee wrote: >>> >>> 于 2014/4/14 21:12, Trond Myklebust 写道: >>>> >>>> On Apr 14, 2014, at 8:59, Kinglong Mee <kinglongmee@xxxxxxxxx> wrote: >>>> >>>>> >>>>> >>>>> 于 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@xxxxxxxxx> 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@xxxxxxxxxxxxxxx> >>>>>> 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. >>>> >>>> Are you running the test as root? The only explanation I can see for should_remove_suid() failing is if the ‘CAP_FSETID’ capability is set. >>> >>> I test it with non-root user, should_remove_suid() also return 0. >> >> OK. Let's make a version that ignores the capabilities, and just tests >> the SUID/SGID bits. > > Due to another problem, test failed again using commands > "echo xxxdsf > testfile; stat testfile". > > In nfs_writeback_done(), nfs_mark_for_revalidate() set cache_validity's > NFS_INO_INVALID_ATTR flag, but nfs4_close_done() will refresh > inode from cache (old mode, not update from server ) and clear > NFS_INO_INVALID_ATTR flags. > > Next, the "stat testfile" gets data from cache, > because NFS_INO_INVALID_ATTR flags is cleared below. > > Calltrace, > [ 4883.997254] nfs4_proc_write_setup > [ 4884.006885] NFS: 1365 nfs_writeback_done (status 11) > [ 4884.008215] nfs4_write_done > [ 4884.009273] nfs4_write_done_cb > [ 4884.010013] nfs_post_op_update_inode_force_wcc > [ 4884.011221] nfs_update_inode > [ 4884.012001] nfs_update_inode > [ 4884.012952] nfs_writeback_done: before nfs_should_remove_suid > [ 4884.014722] nfs_writeback_done: in nfs_should_remove_suid > [ 4884.016549] nfs4_close_done > [ 4884.017614] nfs_refresh_inode > [ 4884.018645] nfs_update_inode > [ 4884.019693] nfs_update_inode > > But, if getting status before close, the mode can be update to latest. Argh. That is a bug in nfs_update_inode(). It is not supposed to clear NFS_INO_INVALID_ATTR if nfs_fattr does not contain a complete set of attributes. Thanks for testing, Kinglong. This is extremely helpful... _________________________________ Trond Myklebust Linux NFS client maintainer, PrimaryData trond.myklebust@xxxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
