From: Jan Kara <jack@suse.cz>
To: Damien Le Moal <Damien.LeMoal@wdc.com>
Cc: Jan Kara <jack@suse.cz>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"hch@infradead.org" <hch@infradead.org>,
Amir Goldstein <amir73il@gmail.com>,
Dave Chinner <david@fromorbit.com>, Ted Tso <tytso@mit.edu>,
Johannes Thumshirn <jth@kernel.org>
Subject: Re: [PATCH 06/12] zonefs: Convert to using invalidate_lock
Date: Mon, 26 Apr 2021 18:24:29 +0200 [thread overview]
Message-ID: <20210426162429.GC23895@quack2.suse.cz> (raw)
In-Reply-To: <BL0PR04MB651475DE7CA7465849D821D5E7429@BL0PR04MB6514.namprd04.prod.outlook.com>
On Mon 26-04-21 06:40:27, Damien Le Moal wrote:
> On 2021/04/24 2:30, Jan Kara wrote:
> > Use invalidate_lock instead of zonefs' private i_mmap_sem. The intended
> > purpose is exactly the same. By this conversion we also fix a race
> > between hole punching and read(2) / readahead(2) paths that can lead to
> > stale page cache contents.
>
> zonefs does not support hole punching since the blocks of a file are determined
> by the device zone configuration and cannot change, ever. So I think you can
> remove the second sentence above.
Sure, thanks for correction. Updated.
Honza
>
> >
> > CC: Damien Le Moal <damien.lemoal@wdc.com>
> > CC: Johannes Thumshirn <jth@kernel.org>
> > CC: <linux-fsdevel@vger.kernel.org>
> > Signed-off-by: Jan Kara <jack@suse.cz>
> > ---
> > fs/zonefs/super.c | 23 +++++------------------
> > fs/zonefs/zonefs.h | 7 +++----
> > 2 files changed, 8 insertions(+), 22 deletions(-)
> >
> > diff --git a/fs/zonefs/super.c b/fs/zonefs/super.c
> > index 049e36c69ed7..60ac5587c880 100644
> > --- a/fs/zonefs/super.c
> > +++ b/fs/zonefs/super.c
> > @@ -462,7 +462,7 @@ static int zonefs_file_truncate(struct inode *inode, loff_t isize)
> > inode_dio_wait(inode);
> >
> > /* Serialize against page faults */
> > - down_write(&zi->i_mmap_sem);
> > + down_write(&inode->i_mapping->invalidate_lock);
> >
> > /* Serialize against zonefs_iomap_begin() */
> > mutex_lock(&zi->i_truncate_mutex);
> > @@ -500,7 +500,7 @@ static int zonefs_file_truncate(struct inode *inode, loff_t isize)
> >
> > unlock:
> > mutex_unlock(&zi->i_truncate_mutex);
> > - up_write(&zi->i_mmap_sem);
> > + up_write(&inode->i_mapping->invalidate_lock);
> >
> > return ret;
> > }
> > @@ -575,18 +575,6 @@ static int zonefs_file_fsync(struct file *file, loff_t start, loff_t end,
> > return ret;
> > }
> >
> > -static vm_fault_t zonefs_filemap_fault(struct vm_fault *vmf)
> > -{
> > - struct zonefs_inode_info *zi = ZONEFS_I(file_inode(vmf->vma->vm_file));
> > - vm_fault_t ret;
> > -
> > - down_read(&zi->i_mmap_sem);
> > - ret = filemap_fault(vmf);
> > - up_read(&zi->i_mmap_sem);
> > -
> > - return ret;
> > -}
> > -
> > static vm_fault_t zonefs_filemap_page_mkwrite(struct vm_fault *vmf)
> > {
> > struct inode *inode = file_inode(vmf->vma->vm_file);
> > @@ -607,16 +595,16 @@ static vm_fault_t zonefs_filemap_page_mkwrite(struct vm_fault *vmf)
> > file_update_time(vmf->vma->vm_file);
> >
> > /* Serialize against truncates */
> > - down_read(&zi->i_mmap_sem);
> > + down_read(&inode->i_mapping->invalidate_lock);
> > ret = iomap_page_mkwrite(vmf, &zonefs_iomap_ops);
> > - up_read(&zi->i_mmap_sem);
> > + up_read(&inode->i_mapping->invalidate_lock);
> >
> > sb_end_pagefault(inode->i_sb);
> > return ret;
> > }
> >
> > static const struct vm_operations_struct zonefs_file_vm_ops = {
> > - .fault = zonefs_filemap_fault,
> > + .fault = filemap_fault,
> > .map_pages = filemap_map_pages,
> > .page_mkwrite = zonefs_filemap_page_mkwrite,
> > };
> > @@ -1158,7 +1146,6 @@ static struct inode *zonefs_alloc_inode(struct super_block *sb)
> >
> > inode_init_once(&zi->i_vnode);
> > mutex_init(&zi->i_truncate_mutex);
> > - init_rwsem(&zi->i_mmap_sem);
> > zi->i_wr_refcnt = 0;
> >
> > return &zi->i_vnode;
> > diff --git a/fs/zonefs/zonefs.h b/fs/zonefs/zonefs.h
> > index 51141907097c..7b147907c328 100644
> > --- a/fs/zonefs/zonefs.h
> > +++ b/fs/zonefs/zonefs.h
> > @@ -70,12 +70,11 @@ struct zonefs_inode_info {
> > * and changes to the inode private data, and in particular changes to
> > * a sequential file size on completion of direct IO writes.
> > * Serialization of mmap read IOs with truncate and syscall IO
> > - * operations is done with i_mmap_sem in addition to i_truncate_mutex.
> > - * Only zonefs_seq_file_truncate() takes both lock (i_mmap_sem first,
> > - * i_truncate_mutex second).
> > + * operations is done with invalidate_lock in addition to
> > + * i_truncate_mutex. Only zonefs_seq_file_truncate() takes both lock
> > + * (invalidate_lock first, i_truncate_mutex second).
> > */
> > struct mutex i_truncate_mutex;
> > - struct rw_semaphore i_mmap_sem;
> >
> > /* guarded by i_truncate_mutex */
> > unsigned int i_wr_refcnt;
> >
>
>
> --
> Damien Le Moal
> Western Digital Research
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2021-04-26 16:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 17:29 [PATCH 0/12 v4] fs: Hole punch vs page cache filling races Jan Kara
2021-04-23 17:29 ` [PATCH 01/12] mm: Fix comments mentioning i_mutex Jan Kara
2021-04-23 17:29 ` [PATCH 02/12] mm: Protect operations adding pages to page cache with invalidate_lock Jan Kara
2021-04-23 18:30 ` Matthew Wilcox
2021-04-23 23:04 ` Dave Chinner
2021-04-26 15:46 ` Jan Kara
2021-04-23 17:29 ` [PATCH 03/12] ext4: Convert to use mapping->invalidate_lock Jan Kara
2021-04-23 17:29 ` [PATCH 04/12] ext2: Convert to using invalidate_lock Jan Kara
2021-04-23 17:29 ` [PATCH 05/12] xfs: Convert to use invalidate_lock Jan Kara
2021-04-23 22:39 ` Dave Chinner
2021-04-23 17:29 ` [PATCH 06/12] zonefs: Convert to using invalidate_lock Jan Kara
2021-04-26 6:40 ` Damien Le Moal
2021-04-26 16:24 ` Jan Kara [this message]
2021-04-23 17:29 ` [PATCH 07/12] f2fs: " Jan Kara
2021-04-23 19:15 ` kernel test robot
2021-04-23 20:05 ` kernel test robot
2021-04-23 17:29 ` [PATCH 08/12] fuse: " Jan Kara
2021-04-23 17:29 ` [PATCH 09/12] shmem: " Jan Kara
2021-04-29 4:12 ` Hugh Dickins
2021-04-29 9:30 ` Jan Kara
2021-04-23 17:29 ` [PATCH 10/12] shmem: Use invalidate_lock to protect fallocate Jan Kara
2021-04-23 19:27 ` kernel test robot
2021-04-29 3:24 ` Hugh Dickins
2021-04-29 9:20 ` Jan Kara
2021-04-23 17:29 ` [PATCH 11/12] ceph: Fix race between hole punch and page fault Jan Kara
2021-04-23 17:29 ` [PATCH 12/12] cifs: " Jan Kara
2021-04-23 22:07 ` [PATCH 0/12 v4] fs: Hole punch vs page cache filling races Dave Chinner
2021-04-23 23:51 ` Matthew Wilcox
2021-04-24 6:11 ` Christoph Hellwig
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=20210426162429.GC23895@quack2.suse.cz \
--to=jack@suse.cz \
--cc=Damien.LeMoal@wdc.com \
--cc=amir73il@gmail.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=jth@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).