From: Omar Sandoval <osandov@osandov.com>
To: Anand Jain <anand.jain@oracle.com>
Cc: Chris Mason <clm@fb.com>,
linux-btrfs@vger.kernel.org, Liu Bo <bo.li.liu@oracle.com>,
Christoph Hellwig <hch@lst.de>, Pat Erley <pat-lkml@erley.org>,
kernel-team@fb.com
Subject: Re: [PATCH v2] Btrfs: fix btrfs_decompress_buf2page()
Date: Wed, 15 Feb 2017 13:57:22 -0800 [thread overview]
Message-ID: <20170215215722.GA11161@vader> (raw)
In-Reply-To: <cdac0f8a-2957-5346-66aa-b890162c2c6e@oracle.com>
On Wed, Feb 15, 2017 at 11:32:06AM +0800, Anand Jain wrote:
> Thanks Omar for nailing this down. How about a test case for this ?
Yeah, I'll put together a test case using your new compressible data
helper, thanks for adding that.
prev parent reply other threads:[~2017-02-15 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 23:03 [PATCH v2] Btrfs: fix btrfs_decompress_buf2page() Omar Sandoval
2017-02-10 23:08 ` Omar Sandoval
[not found] ` <1e52505b-b6fa-f60c-92d5-282ef25cbb9a@erley.org>
2017-02-11 13:07 ` Chris Mason
2017-02-15 3:32 ` Anand Jain
2017-02-15 21:57 ` Omar Sandoval [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=20170215215722.GA11161@vader \
--to=osandov@osandov.com \
--cc=anand.jain@oracle.com \
--cc=bo.li.liu@oracle.com \
--cc=clm@fb.com \
--cc=hch@lst.de \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=pat-lkml@erley.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).