On Mon, Apr 13, 2015 at 12:58 PM, Greg KH <gre...@linuxfoundation.org> wrote: > On Mon, Apr 13, 2015 at 07:28:38PM +0500, Roman Mamedov wrote: >> On Thu, 2 Apr 2015 10:17:47 -0400 >> Chris Mason <c...@fb.com> wrote: >> >> > Hi stable friends, >> > >> > Can you please backport this one to 3.19.y. It fixes a bug introduced >> > by: >> > >> > 381cf6587f8a8a8e981bc0c1aaaa8859b51dc756, which was tagged for stable >> > 3.14+ >> > >> > The symptoms of the bug are deadlocks during log reply after a crash. >> > The patch wasn't intentionally fixing the deadlock, which is why we >> > missed it when tagging fixes. >> >> Unfortunately still not fixed (no btrfs-related changes) in 3.14.38 and >> 3.18.11 released today. > > I have a few hundred stable backports left to sort through, don't worry, > this is still in the queue, it's not lost.
It looks like this still isn't in 3.18.12, though it looks like it is in 3.19.5. -- Rich -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
