linux-kernel - [GIT PULL] Btrfs fixes

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20130317123444.GA3300@shiny.masoncoding.com>
Date:	Sun, 17 Mar 2013 08:34:44 -0400
From:	Chris Mason <chris.mason@...ionio.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	<linux-kernel@...r.kernel.org>, <linux-btrfs@...r.kernel.org>
Subject: [GIT PULL] Btrfs fixes

Hi Linus,

My for-linus branch has some btrfs fixes:

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

Eric's rcu barrier patch fixes a long standing problem with our unmount
code hanging on to devices in workqueue helpers.  Liu Bo nailed down a
difficult assertion for in-memory extent mappings.

Liu Bo (4) commits (+9/-7):
    Btrfs: get better concurrency for snapshot-aware defrag work (+3/-0)
    Btrfs: fix warning when creating snapshots (+5/-6)
    Btrfs: fix warning of free_extent_map (+1/-0)
    Btrfs: remove btrfs_try_spin_lock (+0/-1)

Josef Bacik (1) commits (+4/-1):
    Btrfs: return EIO if we have extent tree corruption

Eric Sandeen (1) commits (+6/-0):
    btrfs: use rcu_barrier() to wait for bdev puts at unmount

Wang Shilong (1) commits (+6/-4):
    Btrfs: return as soon as possible when edquot happens

Total: (7) commits (+25/-12)

 fs/btrfs/extent-tree.c |  5 ++++-
 fs/btrfs/file.c        |  1 +
 fs/btrfs/inode.c       |  3 +++
 fs/btrfs/locking.h     |  1 -
 fs/btrfs/qgroup.c      | 10 ++++++----
 fs/btrfs/transaction.c | 11 +++++------
 fs/btrfs/volumes.c     |  6 ++++++
 7 files changed, 25 insertions(+), 12 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/