linux-kernel - [GIT PULL] Btrfs updates for 2.6.29-rc

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>] [day] [month] [year] [list]

Date:	Thu, 26 Feb 2009 10:09:00 -0500
From:	Chris Mason <chris.mason@...cle.com>
To:	torvalds@...nsmeta.com, linux-kernel <linux-kernel@...r.kernel.org>
Subject: [GIT PULL] Btrfs updates for 2.6.29-rc

Hello everyone,

We've had good results in testing Josef's initial enospc support for
btrfs.  This mainly deals with better accounting of the data extents
that have been allocated for delalloc, and properly returning enospc for
new data writes that can't possibly succeed.

There is some metadata enospc support as well, but there is more work to
be done in that area.  Because this code changes the time at which some
deep call chains are done, it also cuts down on the btrfs stack usage.

Linus, if you pull the master branch of:

git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git

You'll find:

Josef Bacik (2):
      Btrfs: add better -ENOSPC handling
      Btrfs: try committing transaction before returning ENOSPC

 b/fs/btrfs/btrfs_inode.h |    8 +
 b/fs/btrfs/ctree.h       |   40 ++++++--
 b/fs/btrfs/extent-tree.c |   57 ++++++++++--
 b/fs/btrfs/file.c        |   16 ++-
 b/fs/btrfs/inode.c       |   62 +++----------
 b/fs/btrfs/ioctl.c       |    6 -
 fs/btrfs/extent-tree.c   |  215
+++++++++++++++++++++++++++++++++++++++++++----
 7 files changed, 318 insertions(+), 86 deletions(-)

--
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/