From: Chandan Rajendra <chandan@linux.vnet.ibm.com>
To: fdmanana@gmail.com
Cc: fstests@vger.kernel.org,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
chandan@mykolab.com
Subject: Re: [RFC PATCH] btrfs/052: Fix test case to work on variable block size.
Date: Thu, 26 Mar 2015 16:45:35 +0530 [thread overview]
Message-ID: <2036702.tCVM0VzSki@localhost.localdomain> (raw)
In-Reply-To: <CAL3q7H5Nhzyii3PkYAas+Fe6iQWrunRh_XRa6D8Pazt9MwdoyQ@mail.gmail.com>
Hello Filipe,
On Thursday 26 Mar 2015 10:59:28 Filipe David Manana wrote:
> On Thu, Mar 26, 2015 at 9:07 AM, Chandan Rajendra
>
> <chandan@linux.vnet.ibm.com> wrote:
> > The test case passes file offsets which are aligned to 4k block size.
> > This
> > causes btrfs_ioctl_clone() to return with -EINVAL for larger block sizes.
> > Fix this by computing file offsets at run time based on the block size of
> > the underlying filesystem.
> >
> > Signed-off-by: Chandan Rajendra <chandan@linux.vnet.ibm.com>
> >
> >
> >
> > ---
> > There are some more test cases which assume 4k as the underlying
> > filesystem's block size. I am planning to fix them using the
> > final solution agreed upon by the community.
>
> Seems fine to me. Only one minor comment below.
> You should have mentioned that this patch supersedes your previous
> patch https://patchwork.kernel.org/patch/5908801/
Sorry about that. I will mention this when I post the patchset again and also
put differing messages for the two 'Mismatching hash value' cases.
--
chandan
prev parent reply other threads:[~2015-03-26 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 9:07 [RFC PATCH] btrfs/052: Fix test case to work on variable block size Chandan Rajendra
2015-03-26 10:59 ` Filipe David Manana
2015-03-26 11:15 ` Chandan Rajendra [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=2036702.tCVM0VzSki@localhost.localdomain \
--to=chandan@linux.vnet.ibm.com \
--cc=chandan@mykolab.com \
--cc=fdmanana@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@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