Chris Murphy posted on Fri, 27 Jun 2014 09:52:46 -0600 as excerpted: > On Jun 27, 2014, at 9:14 AM, Rich Freeman <r-bt...@thefreemanclan.net> > wrote: > >> On Fri, Jun 27, 2014 at 9:06 AM, Duncan <1i5t5.dun...@cox.net> wrote: >>> Hopefully that problem's fixed on 3.16-rc2+, but as of yet there's not >>> enough 3.16-rc2+ reports out there from folks experiencing issues with >>> 3.15 blocked tasks to rightfully say. >> >> Any chance that it was backported to 3.15.2? I'd rather not move to >> mainline just for btrfs. > > The backports don't happen that quickly.
The lockup bug that affected early 3.16 was introduced in the commit- window pull for 3.16, so the fix for that shouldn't have needed backported (unless the problem commit ended up in stable too, which I doubt but don't know for sure). 3.15.0 didn't contain that bug, which affected me, but as I said, there did seem to be more blocked-task reports in 3.15, which didn't affect me. I didn't run 3.15.1, however, staying on 3.15.0 until after 3.16-rc2 fixed the earlier 3.16-pre series bug that had kept me from the 3.16 series until then. So anything that might have affected the 3.15 stable series after 3.15.0, I wouldn't know about. If I'm not mistaken the fix for the 3.16 series bug was: ea4ebde02e08558b020c4b61bb9a4c0fcf63028e Btrfs: fix deadlocks with trylock on tree nodes. But I think the 3.16 commit-window changes introducing the bug weren't btrfs specific but instead at the generic vfs level. If that's the case, then it's possible that the bug was there before 3.16's commit window and might have been triggering some of the 3.15 reports as well, and the 3.16 vfs change simply made it much worse. IOW, I don't know whether that 3.16 series fix will help 3.15 or not, but I don't believe it'll hurt, and it /might/ help. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- 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
