From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: axboe@kernel.dk, lucho@ionkov.net, jack@suse.cz,
ericvh@gmail.com, tytso@mit.edu, viro@zeniv.linux.org.uk,
rminnich@sandia.gov, martin.petersen@oracle.com, neilb@suse.de,
david@fromorbit.com, gnehzuil.liu@gmail.com,
linux-kernel@vger.kernel.org, hch@infradead.org,
linux-fsdevel@vger.kernel.org, adilger.kernel@dilger.ca,
bharrosh@panasas.com, jlayton@samba.org,
linux-ext4@vger.kernel.org, hirofumi@mail.parknet.co.jp
Subject: Re: [PATCH 2/6] mm: Only enforce stable page writes if the backing device requires it
Date: Thu, 17 Jan 2013 17:26:36 -0800 [thread overview]
Message-ID: <20130118012636.GN6426@blackbox.djwong.org> (raw)
In-Reply-To: <1358247566.2728.12.camel@menhir>
On Tue, Jan 15, 2013 at 10:59:26AM +0000, Steven Whitehouse wrote:
> Hi,
>
> On Mon, 2013-01-14 at 21:42 -0800, Darrick J. Wong wrote:
> > Create a helper function to check if a backing device requires stable page
> > writes and, if so, performs the necessary wait. Then, make it so that all
> > points in the memory manager that handle making pages writable use the helper
> > function. This should provide stable page write support to most filesystems,
> > while eliminating unnecessary waiting for devices that don't require the
> > feature.
> >
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> > ---
> > fs/buffer.c | 2 +-
> > fs/ext4/inode.c | 2 +-
> > fs/gfs2/file.c | 2 +-
> > fs/nilfs2/file.c | 2 +-
> > include/linux/pagemap.h | 1 +
> > mm/filemap.c | 3 ++-
> > mm/page-writeback.c | 20 ++++++++++++++++++++
> > 7 files changed, 27 insertions(+), 5 deletions(-)
> >
> Acked-by: Steven Whitehouse <swhiteho@redhat.com>
>
> Are there any other places that need patching in order to have stable
> page writes working with GFS2? Do we need to unmap in certain places or
> are the hooks for that already in the core code?
>From my semi-brief readthrough of gfs2, I think it's fine, though if you want
to test, you could create a "DIF" checksumming disk via scsi-debug:
# modprobe scsi-debug dif=1 dix=199 ato=1 [more params...]
and create a gfs2 instance atop that.
One other thing to look for is writing metadata objects to buffer_heads or
pages without locking them first. If the fs is dirtying metadata concurrent
with it being written out to disk, that'll cause problems.
Thanks for testing!
--D
>
> Steve.
>
> >
> > diff --git a/fs/buffer.c b/fs/buffer.c
> > index c017a2d..2981449 100644
> > --- a/fs/buffer.c
> > +++ b/fs/buffer.c
> > @@ -2359,7 +2359,7 @@ int __block_page_mkwrite(struct vm_area_struct *vma, struct vm_fault *vmf,
> > if (unlikely(ret < 0))
> > goto out_unlock;
> > set_page_dirty(page);
> > - wait_on_page_writeback(page);
> > + wait_for_stable_page(page);
> > return 0;
> > out_unlock:
> > unlock_page(page);
> > diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
> > index cbfe13b..cd818d8b 100644
> > --- a/fs/ext4/inode.c
> > +++ b/fs/ext4/inode.c
> > @@ -4968,7 +4968,7 @@ int ext4_page_mkwrite(struct vm_area_struct *vma, struct vm_fault *vmf)
> > 0, len, NULL,
> > ext4_bh_unmapped)) {
> > /* Wait so that we don't change page under IO */
> > - wait_on_page_writeback(page);
> > + wait_for_stable_page(page);
> > ret = VM_FAULT_LOCKED;
> > goto out;
> > }
> > diff --git a/fs/gfs2/file.c b/fs/gfs2/file.c
> > index 991ab2d..b9e0ca2 100644
> > --- a/fs/gfs2/file.c
> > +++ b/fs/gfs2/file.c
> > @@ -483,7 +483,7 @@ out:
> > gfs2_holder_uninit(&gh);
> > if (ret == 0) {
> > set_page_dirty(page);
> > - wait_on_page_writeback(page);
> > + wait_for_stable_page(page);
> > }
> > sb_end_pagefault(inode->i_sb);
> > return block_page_mkwrite_return(ret);
> > diff --git a/fs/nilfs2/file.c b/fs/nilfs2/file.c
> > index 6194688..bec4af6 100644
> > --- a/fs/nilfs2/file.c
> > +++ b/fs/nilfs2/file.c
> > @@ -126,7 +126,7 @@ static int nilfs_page_mkwrite(struct vm_area_struct *vma, struct vm_fault *vmf)
> > nilfs_transaction_commit(inode->i_sb);
> >
> > mapped:
> > - wait_on_page_writeback(page);
> > + wait_for_stable_page(page);
> > out:
> > sb_end_pagefault(inode->i_sb);
> > return block_page_mkwrite_return(ret);
> > diff --git a/include/linux/pagemap.h b/include/linux/pagemap.h
> > index 6da609d..0e38e13 100644
> > --- a/include/linux/pagemap.h
> > +++ b/include/linux/pagemap.h
> > @@ -414,6 +414,7 @@ static inline void wait_on_page_writeback(struct page *page)
> > }
> >
> > extern void end_page_writeback(struct page *page);
> > +void wait_for_stable_page(struct page *page);
> >
> > /*
> > * Add an arbitrary waiter to a page's wait queue
> > diff --git a/mm/filemap.c b/mm/filemap.c
> > index 83efee7..5577dc8 100644
> > --- a/mm/filemap.c
> > +++ b/mm/filemap.c
> > @@ -1728,6 +1728,7 @@ int filemap_page_mkwrite(struct vm_area_struct *vma, struct vm_fault *vmf)
> > * see the dirty page and writeprotect it again.
> > */
> > set_page_dirty(page);
> > + wait_for_stable_page(page);
> > out:
> > sb_end_pagefault(inode->i_sb);
> > return ret;
> > @@ -2274,7 +2275,7 @@ repeat:
> > return NULL;
> > }
> > found:
> > - wait_on_page_writeback(page);
> > + wait_for_stable_page(page);
> > return page;
> > }
> > EXPORT_SYMBOL(grab_cache_page_write_begin);
> > diff --git a/mm/page-writeback.c b/mm/page-writeback.c
> > index 0713bfb..9c5af4d 100644
> > --- a/mm/page-writeback.c
> > +++ b/mm/page-writeback.c
> > @@ -2289,3 +2289,23 @@ int mapping_tagged(struct address_space *mapping, int tag)
> > return radix_tree_tagged(&mapping->page_tree, tag);
> > }
> > EXPORT_SYMBOL(mapping_tagged);
> > +
> > +/**
> > + * wait_for_stable_page() - wait for writeback to finish, if necessary.
> > + * @page: The page to wait on.
> > + *
> > + * This function determines if the given page is related to a backing device
> > + * that requires page contents to be held stable during writeback. If so, then
> > + * it will wait for any pending writeback to complete.
> > + */
> > +void wait_for_stable_page(struct page *page)
> > +{
> > + struct address_space *mapping = page_mapping(page);
> > + struct backing_dev_info *bdi = mapping->backing_dev_info;
> > +
> > + if (!bdi_cap_stable_pages_required(bdi))
> > + return;
> > +
> > + wait_on_page_writeback(page);
> > +}
> > +EXPORT_SYMBOL_GPL(wait_for_stable_page);
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2013-01-18 1:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 5:42 [PATCH v2.4 0/3] mm/fs: Remove unnecessary waiting for stable pages Darrick J. Wong
2013-01-15 5:42 ` [PATCH 1/6] bdi: Allow block devices to say that they require stable page writes Darrick J. Wong
2013-01-15 5:42 ` [PATCH 2/6] mm: Only enforce stable page writes if the backing device requires it Darrick J. Wong
2013-01-15 10:19 ` Jan Kara
2013-01-15 10:59 ` Steven Whitehouse
2013-01-18 1:26 ` Darrick J. Wong [this message]
2013-01-15 5:42 ` [PATCH 3/6] 9pfs: Fix filesystem to wait for stable page writeback Darrick J. Wong
2013-01-15 5:43 ` [PATCH 4/6] block: Optionally snapshot page contents to provide stable pages during write Darrick J. Wong
2013-01-16 2:00 ` Jan Kara
2013-01-17 3:01 ` Darrick J. Wong
2013-01-17 3:26 ` Martin K. Petersen
2013-01-17 10:32 ` Jan Kara
2013-01-15 5:43 ` [PATCH 5/6] ocfs2: Wait for page writeback to provide stable pages Darrick J. Wong
2013-01-15 10:15 ` Jan Kara
2013-01-15 5:43 ` [PATCH 6/6] ubifs: " Darrick J. Wong
2013-01-15 22:46 ` [PATCH v2.4 0/3] mm/fs: Remove unnecessary waiting for " Andrew Morton
2013-01-16 0:22 ` Darrick J. Wong
2013-01-16 0:33 ` Andrew Morton
2013-01-17 2:49 ` Darrick J. Wong
2013-01-17 4:43 ` Andrew Morton
2013-01-18 1:18 ` Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2013-01-19 1:12 [PATCH v2.5 " Darrick J. Wong
2013-01-19 1:12 ` [PATCH 2/6] mm: Only enforce stable page writes if the backing device requires it Darrick J. Wong
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=20130118012636.GN6426@blackbox.djwong.org \
--to=darrick.wong@oracle.com \
--cc=adilger.kernel@dilger.ca \
--cc=axboe@kernel.dk \
--cc=bharrosh@panasas.com \
--cc=david@fromorbit.com \
--cc=ericvh@gmail.com \
--cc=gnehzuil.liu@gmail.com \
--cc=hch@infradead.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jack@suse.cz \
--cc=jlayton@samba.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=martin.petersen@oracle.com \
--cc=neilb@suse.de \
--cc=rminnich@sandia.gov \
--cc=swhiteho@redhat.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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).