From: Christoph Hellwig <hch@infradead.org>
To: David Chinner <dgc@sgi.com>
Cc: xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: Review - writing to multiple non-contiguous unwritten extents within a page is broken.
Date: Mon, 4 Jun 2007 15:50:54 +0100 [thread overview]
Message-ID: <20070604145054.GA28033@infradead.org> (raw)
In-Reply-To: <20070523092103.GT85884050@sgi.com>
On Wed, May 23, 2007 at 07:21:03PM +1000, David Chinner wrote:
> Index: 2.6.x-xfs-new/fs/xfs/linux-2.6/xfs_aops.c
> ===================================================================
> --- 2.6.x-xfs-new.orig/fs/xfs/linux-2.6/xfs_aops.c 2007-05-23 16:33:04.000000000 +1000
> +++ 2.6.x-xfs-new/fs/xfs/linux-2.6/xfs_aops.c 2007-05-23 17:52:15.540456674 +1000
> @@ -1008,6 +1008,8 @@ xfs_page_state_convert(
> if (buffer_unwritten(bh) || buffer_delay(bh) ||
> ((buffer_uptodate(bh) || PageUptodate(page)) &&
> !buffer_mapped(bh) && (unmapped || startio))) {
> + int new_ioend = 0;
> +
> /*
> * Make sure we don't use a read-only iomap
> */
> @@ -1026,6 +1028,15 @@ xfs_page_state_convert(
> }
>
> if (!iomap_valid) {
> + /*
> + * if we didn't have a valid mapping then we
> + * need to ensure that we put the new mapping
> + * in a new ioend structure. This needs to be
> + * done to ensure that the ioends correctly
> + * reflect the block mappings at io completion
> + * for unwritten extent conversion.
> + */
> + new_ioend = 1;
> if (type == IOMAP_NEW) {
> size = xfs_probe_cluster(inode,
> page, bh, head, 0);
> @@ -1045,7 +1056,7 @@ xfs_page_state_convert(
> if (startio) {
> xfs_add_to_ioend(inode, bh, offset,
> type, &ioend,
> - !iomap_valid);
> + new_ioend);
Looks good. I'm pretty sure that we had something like a new_ioend variable
in the initial versions of this code, but I don't know when and why we
got rid of it.
prev parent reply other threads:[~2007-06-04 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 9:21 Review - writing to multiple non-contiguous unwritten extents within a page is broken David Chinner
2007-06-04 4:53 ` David Chinner
2007-06-04 14:50 ` Christoph Hellwig [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=20070604145054.GA28033@infradead.org \
--to=hch@infradead.org \
--cc=dgc@sgi.com \
--cc=xfs-dev@sgi.com \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.