public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Lachlan McIlroy <lachlan@sgi.com>
To: David Chinner <dgc@sgi.com>
Cc: xfs-dev@sgi.com, xfs@oss.sgi.com
Subject: Re: Review: Fix sub-page zeroing for buffered writes into unwritten extents
Date: Wed, 24 Jan 2007 16:44:04 +0000	[thread overview]
Message-ID: <45B78CD4.1060400@sgi.com> (raw)
In-Reply-To: <20070123224704.GH33919298@melbourne.sgi.com>

Dave,

I'm trying to understand what the sequence of events is here.

If we write to an unwritten extent then will __xfs_get_blocks()
be called with create=1 and flags=BMAPI_WRITE?  And calling
bhv_vop_bmap() with flags set to BMAPI_WRITE will cause xfs_iomap()
to set iomap_flags to IOMAP_NEW?  The combination of create=1 and
iomap_flags=IOMAP_NEW in __xfs_get_blocks() should result in calling
set_buffer_new(), right?

I must be missing something...

Lachlan

David Chinner wrote:
> Simple test case:
> 
> prealloc large file
> write 3000 bytes to the middle of the file
> read back file
> 
> The data in the block where the 3000 bytes was written has
> non-zero garbage around it both in memory and on disk.
> 
> The problem is a buffer mapping problem. When we copy data
> into an unwritten buffer, we have the create flag set which
> means we map the buffer. We then mark the buffer as unwritten,
> and do some more checks. Because the buffer is mapped, we do
> not set the buffer_new() flag on the buffer, which means when
> we return to the generic code, it does not do sub-block zeroing
> of the unwritten areas of the block.
> 
> The following patch fixes the problem. Comments?
> 
> Cheers,
> 
> Dave.

  reply	other threads:[~2007-01-24 16:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-23 22:47 Review: Fix sub-page zeroing for buffered writes into unwritten extents David Chinner
2007-01-24 16:44 ` Lachlan McIlroy [this message]
2007-01-28 22:22   ` David Chinner
2007-01-29 12:55     ` Lachlan McIlroy

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=45B78CD4.1060400@sgi.com \
    --to=lachlan@sgi.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox