From: David Disseldorp <ddiss@suse.de>
To: xfs@oss.sgi.com
Cc: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] __btrfs_drop_extents() BUG_ON reproducer
Date: Wed, 5 Feb 2014 12:16:47 +0100 [thread overview]
Message-ID: <1391599009-2402-1-git-send-email-ddiss@suse.de> (raw)
This patch-set provides a reproducer for hitting the 3.14.0-rc1 BUG_ON()
at:
692 int __btrfs_drop_extents(struct btrfs_trans_handle *trans,
...
839 /*
840 * | ---- range to drop ----- |
841 * | -------- extent -------- |
842 */
843 if (start <= key.offset && end < extent_end) {
844 BUG_ON(extent_type == BTRFS_FILE_EXTENT_INLINE);
845
846 memcpy(&new_key, &key, sizeof(new_key));
The first patch adds a small cloner binary which is used by btrfs/035 to
dispatch BTRFS_IOC_CLONE_RANGE requests.
This workload resembles that of Samba's vfs_btrfs module, when a Windows
client restores a file from a shadow-copy (snapshot) using server-side
copy requests.
Feedback appreciated.
Cheers, David
src/Makefile | 2 +-
src/cloner.c | 168 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/035 | 76 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/035.out | 3 +++
tests/btrfs/group | 1 +
5 files changed, 249 insertions(+), 1 deletion(-)
next reply other threads:[~2014-02-05 11:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 11:16 David Disseldorp [this message]
2014-02-05 11:16 ` [PATCH 1/2] btrfs: add small program for clone testing David Disseldorp
2014-02-05 23:09 ` Dave Chinner
2014-02-06 10:03 ` David Disseldorp
2014-02-05 11:16 ` [PATCH 2/2] btrfs/035: add new clone overwrite regression test David Disseldorp
2014-02-05 23:15 ` Dave Chinner
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=1391599009-2402-1-git-send-email-ddiss@suse.de \
--to=ddiss@suse.de \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).