From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: unable to handle kernel paging request
Date: Fri, 16 Sep 2016 02:45:43 +0000 (UTC) [thread overview]
Message-ID: <pan$870ae$e71e207d$86afd0fb$1fb7c517@cox.net> (raw)
In-Reply-To: CAAwVk4kBfG6_A9J8Kc9rFY_CXcekdRyDK37EYe-XqPo6DKwqMw@mail.gmail.com
Mark Gavalda posted on Thu, 15 Sep 2016 22:12:57 +0200 as excerpted:
[Moved to bottom to retain quote/reply order.]
> On Thu, Sep 15, 2016 at 6:05 PM, Chris Mason <clm@fb.com> wrote:
>> On 09/15/2016 10:08 AM, Mark Gavalda wrote:
>>>
>>> Hi,
>>>
>>> Bumped into the following one today; kernel 4.4.0-36-generic Ubuntu
>>> 16.4.1; CPU went to 100% and only a hard restart solved the issue.
>>> Since then everything's back to normal.
>>>
>>> Please let me know how can I help get to the bottom of this?
>>
>>
>> I saw similar traces when tracking down this bug:
>>
>> https://git.kernel.org/cgit/linux/kernel/git/mason/linux-btrfs.git/
commit/?h=for-linus-4.8&id=cbd60aa7cd17d81a434234268c55192862147439
>>
>> It's flagged for stable, so you'll get it with the next stable update,
>> or you can apply it by hand and rebuild.
> Thanks, I can see it included in 4.8-rc6 but not the other branches.
> Will it get pulled later or is this a 4.8 only fix?
Flagged for stable means it's headed to the maintained stable branches
(well, the ones to which the fix applies for regression fixes, but
definitely 4.4 LTS series in this case since Chris Mason indicated it
should apply in your case), not just current.
But stabilization policy says a patch must hit mainline current first,
before it is eligible for older stable as well. So it would be
/expected/ to hit 4.8-rc, current development, first. After that, given
that it's already flagged for stable, it should eventually hit all the
stable kernels to which it applies as well. That can be right away, but
if the stable maintainer (Greg K-H, normally) is backlogged due to just
getting back from vacation or something, as sometimes happens, it can
take a few weeks to work thru the backlog, so it can take a bit, as well.
--
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
prev parent reply other threads:[~2016-09-16 2:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 14:08 unable to handle kernel paging request Mark Gavalda
2016-09-15 16:05 ` Chris Mason
2016-09-15 20:12 ` Mark Gavalda
2016-09-16 2:45 ` Duncan [this message]
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$870ae$e71e207d$86afd0fb$1fb7c517@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).