linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Blocked tasks on 3.15.1
Date: Fri, 27 Jun 2014 17:20:41 +0000 (UTC)	[thread overview]
Message-ID: <pan$26aa0$13a0ca68$c41d00a9$e8c14640@cox.net> (raw)
In-Reply-To: 4623589E-3298-4980-A257-665CFA9FB61B@colorremedies.com

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-btrfs@thefreemanclan.net>
> wrote:
> 
>> On Fri, Jun 27, 2014 at 9:06 AM, Duncan <1i5t5.duncan@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


  reply	other threads:[~2014-06-27 17:20 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27 10:02 Blocked tasks on 3.15.1 Tomasz Chmielewski
2014-06-27 13:06 ` Duncan
2014-06-27 15:14   ` Rich Freeman
2014-06-27 15:52     ` Chris Murphy
2014-06-27 17:20       ` Duncan [this message]
2014-06-28  0:22         ` Chris Samuel
2014-06-29 20:02           ` Cody P Schafer
2014-06-29 22:22             ` Cody P Schafer
2014-06-30 18:11             ` Chris Mason
2014-06-30 18:30               ` Chris Mason
2014-06-30 23:42                 ` Cody P Schafer
2014-07-01 21:04                   ` Chris Mason
2014-07-01 23:05                     ` Cody P Schafer
2014-07-02 12:27                       ` Cody P Schafer
2014-07-02 13:58                         ` Chris Mason
2014-07-02 14:15                           ` Chris Mason
2014-07-17 13:18                             ` Chris Mason
2014-07-19  0:33                               ` Blocked tasks on 3.15.1, raid1 btrfs is no ends of trouble for me Marc MERLIN
2014-07-19  0:44                                 ` Marc MERLIN
2014-07-19  1:58                                   ` Marc MERLIN
2014-07-19  1:59                                   ` Chris Samuel
2014-07-19  5:40                                     ` Marc MERLIN
2014-07-19 17:38                               ` Blocked tasks on 3.15.1 Cody P Schafer
2014-07-19 18:23                                 ` Martin Steigerwald
2014-07-22 14:53                                   ` Chris Mason
2014-07-22 15:14                                     ` Torbjørn
2014-07-22 16:46                                     ` Marc MERLIN
2014-07-22 19:42                                     ` Torbjørn
2014-07-22 19:50                                       ` Chris Mason
2014-07-22 20:10                                         ` Torbjørn
2014-07-22 21:13                                     ` Martin Steigerwald
2014-07-22 21:15                                       ` Chris Mason
2014-07-23 11:13                                         ` Martin Steigerwald
2014-07-23  1:06                                     ` Rich Freeman
2014-07-23  6:38                                       ` Felix Seidel
2014-07-23 13:20                                     ` Charles Cazabon
2014-07-25  2:27                                     ` Cody P Schafer
2014-08-07 15:12                                       ` Tobias Holst
2014-08-07 16:05                                         ` Duncan
2014-08-12  2:55                                     ` Charles Cazabon
2014-08-12  2:56                                       ` Liu Bo
2014-08-12  4:18                                         ` Duncan
2014-08-12  4:49                                       ` Marc MERLIN
2014-08-18 20:34                                         ` James Cloos
2014-07-01  3:06               ` Charles Cazabon
2014-06-30  2:33           ` Rich Freeman
2014-06-27 18:33       ` Rich Freeman
  -- strict thread matches above, loose matches on Subject: below --
2014-07-20 21:34 Matt
2014-06-27  1:37 Rich Freeman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='pan$26aa0$13a0ca68$c41d00a9$e8c14640@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).