From: Wade Cline <clinew@linux.vnet.ibm.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: linux-btrfs@vger.kernel.org, mcao@us.ibm.com
Subject: Re: [PATCH] Btrfs: create a pinned em when writing to a prealloc range in DIO
Date: Tue, 11 Sep 2012 15:16:36 -0700 [thread overview]
Message-ID: <504FB844.7000307@linux.vnet.ibm.com> (raw)
In-Reply-To: <1347392531-10863-1-git-send-email-jbacik@fusionio.com>
On 09/11/2012 12:42 PM, Josef Bacik wrote:
> Wade Cline reported a problem where he was getting garbage and warnings when
> writing to a preallocated range via O_DIRECT. This is because we weren't
> creating our normal pinned extent_map for the range we were writing to,
> which was causing all sorts of issues. This patch fixes the problem and
> makes his testcase much happier. Thanks,
>
> Reported-by: Wade Cline<clinew@linux.vnet.ibm.com>
> Signed-off-by: Josef Bacik<jbacik@fusionio.com>
I ran some basic tests and this seems to have fixed the issue.
Tested-by: Wade Cline <clinew@linux.vnet.ibm.com>
Thank you,
Wade
prev parent reply other threads:[~2012-09-11 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 19:42 [PATCH] Btrfs: create a pinned em when writing to a prealloc range in DIO Josef Bacik
2012-09-11 22:16 ` Wade Cline [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=504FB844.7000307@linux.vnet.ibm.com \
--to=clinew@linux.vnet.ibm.com \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mcao@us.ibm.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;
as well as URLs for NNTP newsgroup(s).