linux-kernel - Re: [GIT PULL] Btrfs deadlock fix

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

Message-ID: <20141124182734.GE26471@twin.jikos.cz>
Date:	Mon, 24 Nov 2014 19:27:34 +0100
From:	David Sterba <dsterba@...e.cz>
To:	Chris Mason <clm@...com>
Cc:	dsterba@...e.cz, torvalds@...ux-foundation.org,
	linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] Btrfs deadlock fix

On Mon, Nov 24, 2014 at 01:01:10PM -0500, Chris Mason wrote:
> > I've retested it again including this pull and still deadlocks 
> > reliably
> > at btrfs/070.
> 
> This wasn't a new problem, so I had it queued for the merge window.

Well, I don't remember seeing this problem with anything 3.17 based but
I can check. I know this does not mean that it was introduced in 3.18,
only that other changes exposed the problem, but this still IMHO
qualifies as a bug to be fixed within 3.18. Besides, it makes testing
3.18-rc slightly more annoying (either skip the test or manually pick
the patch after each pull).
--
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/