From: Dave Jiang <dave.jiang@intel.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: lczerner@redhat.com, jack@suse.cz, linux-nvdimm@lists.01.org,
david@fromorbit.com, linux-xfs@vger.kernel.org,
zwisler@kernel.org, linux-fsdevel@vger.kernel.org, tytso@mit.edu,
linux-ext4@vger.kernel.org, hch@lst.de
Subject: Re: [PATCH v2 2/2] [PATCH] xfs: Close race between direct IO and xfs_break_layouts()
Date: Fri, 10 Aug 2018 08:54:00 -0700 [thread overview]
Message-ID: <dc539a4d-7f9c-11c6-e63b-93ebb7f7ff9d@intel.com> (raw)
In-Reply-To: <20180810154809.GD15083@magnolia>
On 08/10/2018 08:48 AM, Darrick J. Wong wrote:
> On Wed, Aug 08, 2018 at 10:31:40AM -0700, Dave Jiang wrote:
>> This patch is the duplicate of ross's fix for ext4 for xfs.
>>
>> If the refcount of a page is lowered between the time that it is returned
>> by dax_busy_page() and when the refcount is again checked in
>> xfs_break_layouts() => ___wait_var_event(), the waiting function
>> xfs_wait_dax_page() will never be called. This means that
>> xfs_break_layouts() will still have 'retry' set to false, so we'll stop
>> looping and never check the refcount of other pages in this inode.
>>
>> Instead, always continue looping as long as dax_layout_busy_page() gives us
>> a page which it found with an elevated refcount.
>>
>> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
>> Reviewed-by: Jan Kara <jack@suse.cz>
>> ---
>>
>> Sorry resend, forgot to add Jan's reviewed-by.
>>
>> v2:
>> - Rename parameter from did_unlock to retry (Jan)
>>
>> fs/xfs/xfs_file.c | 9 ++++-----
>> 1 file changed, 4 insertions(+), 5 deletions(-)
>>
>> diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c
>> index a3e7767a5715..cd6f0d8c4922 100644
>> --- a/fs/xfs/xfs_file.c
>> +++ b/fs/xfs/xfs_file.c
>> @@ -721,12 +721,10 @@ xfs_file_write_iter(
>>
>> static void
>> xfs_wait_dax_page(
>> - struct inode *inode,
>> - bool *did_unlock)
>> + struct inode *inode)
>> {
>> struct xfs_inode *ip = XFS_I(inode);
>>
>> - *did_unlock = true;
>> xfs_iunlock(ip, XFS_MMAPLOCK_EXCL);
>> schedule();
>> xfs_ilock(ip, XFS_MMAPLOCK_EXCL);
>> @@ -736,7 +734,7 @@ static int
>> xfs_break_dax_layouts(
>> struct inode *inode,
>> uint iolock,
>> - bool *did_unlock)
>> + bool *retry)
>
> Uhhh, this hunk doesn't apply. xfs_break_dax_layouts doesn't have an
> iolock parameter anymore; was this not generated off of xfs for-next?
Sorry. It was generated against 4.18-rc8. I'll respin patch against xfs
for-next.
>
> --D
>
>> {
>> struct page *page;
>>
>> @@ -746,9 +744,10 @@ xfs_break_dax_layouts(
>> if (!page)
>> return 0;
>>
>> + *retry = true;
>> return ___wait_var_event(&page->_refcount,
>> atomic_read(&page->_refcount) == 1, TASK_INTERRUPTIBLE,
>> - 0, 0, xfs_wait_dax_page(inode, did_unlock));
>> + 0, 0, xfs_wait_dax_page(inode));
>> }
>>
>> int
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2018-08-10 15:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 17:31 [PATCH v2 2/2] [PATCH] xfs: Close race between direct IO and xfs_break_layouts() Dave Jiang
2018-08-10 15:48 ` Darrick J. Wong
2018-08-10 15:54 ` Dave Jiang [this message]
2018-08-10 16:02 ` Darrick J. Wong
2018-08-10 16:05 ` Dave Jiang
2018-08-10 18:31 ` Eric Sandeen
2018-08-10 19:23 ` Dave Jiang
2018-08-10 19:24 ` Ross Zwisler
2018-08-10 19:26 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2018-08-08 17:25 [PATCH v2 1/2] ext4: Close race between direct IO and ext4_break_layouts() Dave Jiang
2018-08-08 17:26 ` [PATCH v2 2/2] [PATCH] xfs: Close race between direct IO and xfs_break_layouts() Dave Jiang
2018-08-09 8:57 ` Jan Kara
2018-08-09 16:21 ` Dave Jiang
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=dc539a4d-7f9c-11c6-e63b-93ebb7f7ff9d@intel.com \
--to=dave.jiang@intel.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=zwisler@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 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).