linux-kernel - Re: Btrfs trees for linux-next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 10 Dec 2008 21:34:56 -0500
From:	Chris Mason <chris.mason@...cle.com>
To:	linux-kernel@...r.kernel.org
Cc:	linux-btrfs@...r.kernel.org,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>, sfr@...b.auug.org.au
Subject: Re: Btrfs trees for linux-next

On Thu, 2008-11-20 at 07:18 -0500, Chris Mason wrote:
> Hello everyone,
> 
> I've updated the btrfs git trees to 2.6.28-rc5 and tested against
> linux-next.
> 
> We've knocked a bunch of things off the todo list since I last posted,
> including compression (mount -o compress) and the ability to create
> subvols and snapshots anywhere in the FS.
> 
> There are a small number of disk format changes pending, which I put off
> in favor of making compression stable/fast.  We'll hammer these out
> shortly.
> 

Just an update, while I still have a long todo list and plenty of things
to fix in the code, these src trees have been updated with a disk format
I hope to maintain compatibility with from here on.  There are still
format changes planned, but should go in through the compat mechanisms
in the sources now.

The btrfs trees are still at 2.6.28-rc5, but I just tested against
linux-next without problems.

> The btrfs kernel code is here:
> http://git.kernel.org/?p=linux/kernel/git/mason/btrfs-unstable.git;a=summary
> 
> And the utilities are here:
> 
> http://git.kernel.org/?p=linux/kernel/git/mason/btrfs-progs-unstable.git;a=summary

-chris


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/