linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: Trond Myklebust <trondmy@primarydata.com>,
	Anna Schumaker <anna.schumaker@netapp.com>
Cc: Olaf Kirch <OKir@suse.com>, NFS List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] NFS: flush data when locking a file to ensure cache coherence for mmap.
Date: Fri, 18 Nov 2016 15:35:27 +1100	[thread overview]
Message-ID: <87eg29flrk.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <877fce8z0o.fsf@notabene.neil.brown.name>

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


PING again

Thanks,
NeilBrown

On Fri, Jul 22 2016, NeilBrown wrote:

> PING .... any comments on this patch, or the problem it tries to
> address?
>
> Thanks,
> NeilBrown
>
>
> On Fri, Jun 03 2016, NeilBrown wrote:
>
>> When a byte range lock (or flock) is taken out on an NFS file, the
>> validity of the cached data is checked and the inode is marked
>> NFS_INODE_INVALID_DATA.  However the cached data isn't flushed from
>> the page cache.
>>
>> This is sufficient for future read() requests or mmap() requests as
>> they call nfs_revalidate_mapping() which performs the flush if
>> necessary.
>>
>> However an existing mapping is not affected.  Accessing data through
>> that mapping will continue to return old data even though the inode is
>> marked NFS_INODE_INVALID_DATA.
>>
>> This can easily be confirmed using the 'nfs' tool in
>>   git://github.com/okirch/twopence-nfs.git
>> and running
>>
>>    nfs coherence FILENAME
>> on one client, and
>>    nfs coherence -r FILENAME
>> on another client.
>>
>> It appears that prior to Linux 2.6.0 this worked correctly.
>>
>> However commit:
>>
>> http://git.kernel.org/cgit/linux/kernel/git/history/history.git/commit/?id=ca9268fe3ddd075714005adecd4afbd7f9ab87d0
>>
>> removed the call to inode_invalidate_pages() from nfs_zap_caches().  I
>> haven't tested this code, but inspection suggests that prior to this
>> commit, file locking would invalidate all inode pages.
>>
>> This patch adds a call to nfs_revalidate_mapping_protected() after a
>> successful SETLK so that invalid data is flushed.  With this patch the
>> above test passes.
>>
>> Cc: Olaf Kirch <okir@suse.com>
>> Signed-off-by: NeilBrown <neilb@suse.com>
>> ---
>>  fs/nfs/file.c | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/fs/nfs/file.c b/fs/nfs/file.c
>> index 717a8d6af52d..781cc6c9c60b 100644
>> --- a/fs/nfs/file.c
>> +++ b/fs/nfs/file.c
>> @@ -822,6 +822,7 @@ do_setlk(struct file *filp, int cmd, struct file_lock *fl, int is_local)
>>  			__nfs_revalidate_inode(NFS_SERVER(inode), inode);
>>  		else
>>  			nfs_zap_caches(inode);
>> +		nfs_revalidate_mapping_protected(inode, filp->f_mapping);
>>  	}
>>  out:
>>  	return status;
>> -- 
>> 2.8.3

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]

      reply	other threads:[~2016-11-18  4:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-03  3:26 [PATCH] NFS: flush data when locking a file to ensure cache coherence for mmap NeilBrown
2016-07-21 21:25 ` NeilBrown
2016-11-18  4:35   ` NeilBrown [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=87eg29flrk.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=OKir@suse.com \
    --cc=anna.schumaker@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trondmy@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).