linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kyle McMartin <kyle@mcmartin.ca>
To: Chris Mason <chris.mason@oracle.com>
Cc: btrfs-devel@oss.oracle.com, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [ANNOUNCE] Btrfs v0.10 (online growing/shrinking, ext3 conversion, and more)
Date: Tue, 15 Jan 2008 11:55:55 -0500	[thread overview]
Message-ID: <20080115165555.GA7164@phobos.i.cabal.ca> (raw)
In-Reply-To: <20080115105238.4fc3e992@think.oraclecorp.com>

On Tue, Jan 15, 2008 at 10:52:38AM -0500, Chris Mason wrote:
> http://oss.oracle.com/projects/btrfs/
> 
> Btrfs is still in an early alpha state, and the disk format is not finalized.
> v0.10 introduces a new disk format, and is not compatible with v0.9.
> 

Looks like fun. btrfsck fails to check if it actually received a
dev argument though, so if you don't pass a device, we get a nice
segfault.

Signed-off-by: Kyle McMartin <kmcmartin@redhat.com>

---
diff -Nur btrfs-progs-0.10/btrfsck.c btrfs-progs-0.10-kyle/btrfsck.c
--- btrfs-progs-0.10/btrfsck.c	2008-01-15 10:33:32.000000000 -0500
+++ btrfs-progs-0.10-kyle/btrfsck.c	2008-01-15 11:49:24.000000000 -0500
@@ -709,6 +709,11 @@
 	return err;
 }
 
+void print_usage(void) {
+	fprintf(stderr, "usage: btrfsck dev\n");
+	exit(1);
+}
+
 int main(int ac, char **av) {
 	struct btrfs_root *root;
 	struct cache_tree extent_cache;
@@ -727,6 +732,9 @@
 	int slot;
 	struct btrfs_root_item ri;
 
+	if (ac < 2)
+		print_usage();
+
 	radix_tree_init();
 	cache_tree_init(&extent_cache);
 	cache_tree_init(&seen);

  reply	other threads:[~2008-01-15 17:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-15 15:52 [ANNOUNCE] Btrfs v0.10 (online growing/shrinking, ext3 conversion, and more) Chris Mason
2008-01-15 16:55 ` Kyle McMartin [this message]
2008-01-16 10:02 ` [Btrfs-devel] " Christian Hesse
2008-01-16 17:50   ` Simon Holm Thøgersen
2008-01-17 18:25 ` Chris mason
2008-01-17 19:28   ` Daniel Phillips
2008-01-17 20:14     ` Chris mason
2008-01-17 23:17   ` Christian Hesse
2008-01-18 13:48     ` Chris mason
2008-01-21  8:57       ` Christian Hesse
2008-01-21  9:15         ` Yan Zheng
2008-01-21 10:32           ` Christian Hesse

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=20080115165555.GA7164@phobos.i.cabal.ca \
    --to=kyle@mcmartin.ca \
    --cc=btrfs-devel@oss.oracle.com \
    --cc=chris.mason@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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).