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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20150515191142.GA13342@ret.thefacebook.com>
Date:	Fri, 15 May 2015 15:11:51 -0400
From:	Chris Mason <clm@...com>
To:	<torvalds@...ux-foundation.org>,
	linux-btrfs <linux-btrfs@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: [GIT PULL] Btrfs fixes

Hi Linus,

I have a few more fixes in my for-linus-4.1 branch:

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

The first commit is a fix from Filipe for a very old extent buffer reuse
race that triggered a BUG_ON.  It hasn't come up often, I looked through
old logs at FB and we hit it a handful of times over the last year.

The rest are other corners he hit during testing

Filipe Manana (4) commits (+68/-10):
    Btrfs: fix race when reusing stale extent buffers that leads to BUG_ON (+19/-0)
    Btrfs: fix race between block group creation and their cache writeout (+27/-4)
    Btrfs: fix panic when starting bg cache writeout after IO error (+10/-4)
    Btrfs: fix crash after inode cache writeback failure (+12/-2)

Total: (4) commits

 fs/btrfs/extent-tree.c      | 31 +++++++++++++++++++++++++++----
 fs/btrfs/extent_io.c        | 19 +++++++++++++++++++
 fs/btrfs/free-space-cache.c | 14 ++++++++++++--
 fs/btrfs/ordered-data.c     | 14 ++++++++++----
 4 files changed, 68 insertions(+), 10 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/