linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Segfault in "btrfs balance start" due to kernel page allocation failure
Date: Sat, 10 Jan 2015 09:28:17 +0000 (UTC)	[thread overview]
Message-ID: <pan$3ea4e$eb4d7d19$bbe46563$3cc96659@cox.net> (raw)
In-Reply-To: m8psfs$h0t$1@ger.gmane.org

Remy Blank posted on Sat, 10 Jan 2015 01:41:31 +0100 as excerpted:

> Maybe it would be worth adding some tests using rsync to the test suite
> (I assume there is one)?

Yes.  xfs-tests (which isn't just for xfs any more, ext4, btrfs, and 
possibly others, use it too).

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2015-01-10  9:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 11:19 Segfault in "btrfs balance start" due to kernel page allocation failure Remy Blank
2015-01-09 22:43 ` Duncan
2015-01-10  0:41   ` Remy Blank
2015-01-10  9:28     ` Duncan [this message]
2015-01-10  9:48     ` Duncan

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='pan$3ea4e$eb4d7d19$bbe46563$3cc96659@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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;
as well as URLs for NNTP newsgroup(s).