All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kinglong Mee <kinglongmee@gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	kinglongmee@gmail.com
Subject: Re: [PATCH] NFSD: Process time setting separately only for nfsv2
Date: Thu, 28 May 2015 08:09:54 +0800	[thread overview]
Message-ID: <55665CD2.9030301@gmail.com> (raw)
In-Reply-To: <20150527183601.GB23302@fieldses.org>

On 5/28/2015 2:36 AM, J. Bruce Fields wrote:
> On Wed, May 27, 2015 at 04:05:10PM +0800, Kinglong Mee wrote:
>> NFSv2 does not different between "set-[ac]time-to-now" which only
>> requires access, and "set-[ac]time-to-X" which requires ownership.
>>
>> But, NFSv3/v4 are support the difference.
>> Just let those codes valid for NFSv2.
> 
> Looks like this is already done by Andreas Gruenbacher's "nfsd: Disable
> NFSv2 timestamp workaround for NFSv3+" in my for-4.2-incoming branch.

Sorry, I find that patch now.
Please ignore this.

> Do you see any problem with that patch?

No,
That patch is great!

thanks,
Kinglong Mee

> 
> --b.
> 
>>
>> Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>
>> ---
>>  fs/nfsd/vfs.c | 7 ++++---
>>  1 file changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/nfsd/vfs.c b/fs/nfsd/vfs.c
>> index 84d770b..bf4a15b 100644
>> --- a/fs/nfsd/vfs.c
>> +++ b/fs/nfsd/vfs.c
>> @@ -300,7 +300,7 @@ commit_metadata(struct svc_fh *fhp)
>>   * NFS semantics and what Linux expects.
>>   */
>>  static void
>> -nfsd_sanitize_attrs(struct inode *inode, struct iattr *iap)
>> +nfsd_sanitize_attrs(struct svc_rqst *rqstp, struct inode *inode, struct iattr *iap)
>>  {
>>  	/*
>>  	 * NFSv2 does not differentiate between "set-[ac]time-to-now"
>> @@ -315,7 +315,8 @@ nfsd_sanitize_attrs(struct inode *inode, struct iattr *iap)
>>  	 */
>>  #define BOTH_TIME_SET (ATTR_ATIME_SET | ATTR_MTIME_SET)
>>  #define	MAX_TOUCH_TIME_ERROR (30*60)
>> -	if ((iap->ia_valid & BOTH_TIME_SET) == BOTH_TIME_SET &&
>> +	if (rqstp->rq_vers == 2 &&
>> +	    (iap->ia_valid & BOTH_TIME_SET) == BOTH_TIME_SET &&
>>  	    iap->ia_mtime.tv_sec == iap->ia_atime.tv_sec) {
>>  		/*
>>  		 * Looks probable.
>> @@ -435,7 +436,7 @@ nfsd_setattr(struct svc_rqst *rqstp, struct svc_fh *fhp, struct iattr *iap,
>>  	if (!iap->ia_valid)
>>  		goto out;
>>  
>> -	nfsd_sanitize_attrs(inode, iap);
>> +	nfsd_sanitize_attrs(rqstp, inode, iap);
>>  
>>  	/*
>>  	 * The size case is special, it changes the file in addition to the
>> -- 
>> 2.4.1
> 

      reply	other threads:[~2015-05-28  0:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27  8:05 [PATCH] NFSD: Process time setting separately only for nfsv2 Kinglong Mee
2015-05-27 18:36 ` J. Bruce Fields
2015-05-28  0:09   ` Kinglong Mee [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=55665CD2.9030301@gmail.com \
    --to=kinglongmee@gmail.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.