From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-xfs@vger.kernel.org, jstancek@redhat.com
Subject: Re: [PATCH] xfs: fix sub-page uptodate handling
Date: Thu, 5 Dec 2019 07:58:20 +1100 [thread overview]
Message-ID: <20191204205820.GN2695@dread.disaster.area> (raw)
In-Reply-To: <20191204172804.6589-1-hch@lst.de>
On Wed, Dec 04, 2019 at 06:28:04PM +0100, Christoph Hellwig wrote:
> bio complentions can race when a page spans more than one file system
> block. Add a spinlock to synchronize marking the page uptodate.
>
> Fixes: 9dc55f1389f9 ("iomap: add support for sub-pagesize buffered I/O without buffer heads")
> Reported-by: Jan Stancek <jstancek@redhat.com>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Looks sane, similar fix to previous completion issues like this.
Reviewed-by: Dave Chinner <dchinner@redhat.com>
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2019-12-04 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 17:28 [PATCH] xfs: fix sub-page uptodate handling Christoph Hellwig
2019-12-04 20:58 ` Dave Chinner [this message]
2019-12-04 21:57 ` Darrick J. Wong
2019-12-05 7:44 ` 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=20191204205820.GN2695@dread.disaster.area \
--to=david@fromorbit.com \
--cc=hch@lst.de \
--cc=jstancek@redhat.com \
--cc=linux-xfs@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 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).