public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: <dsterba@suse.cz>, Dave Jones <davej@codemonkey.org.uk>,
	<jbacik@fb.com>, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [4.1-rc7] btrfs related VM_BUG_ON in filemap.c
Date: Tue, 16 Jun 2015 13:19:20 -0400	[thread overview]
Message-ID: <55805A98.9020609@fb.com> (raw)
In-Reply-To: <20150616171443.GS6761@suse.cz>

On 06/16/2015 01:14 PM, David Sterba wrote:
> On Wed, Jun 10, 2015 at 01:43:31PM -0400, Chris Mason wrote:
>> On 06/10/2015 09:40 AM, Dave Jones wrote:
>>> Found this on serial console this morning. The machine had rebooted itself shortly
>>> afterwards (surprising, given I don't have panic-on-oops or similar set).
>>>
>>
>> We had one other report of this a few months ago.  Josef and I read
>> through all of this and decided it was impossible, so someone else must
>> be holding on to that page and unlocking it.
>>
>> (that someone else could easily be btrfs, just not in this code path)
> 
> https://patchwork.kernel.org/patch/6478941/ looks like the fix, bug
> symptoms match the "keywords", I haven't inspected it closely.
> 

That one is in my integration-4.2 branch if you want to give it a shot.

-chris

  reply	other threads:[~2015-06-16 17:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10 13:40 [4.1-rc7] btrfs related VM_BUG_ON in filemap.c Dave Jones
2015-06-10 17:43 ` Chris Mason
2015-06-10 18:42   ` Dave Jones
2015-06-16 17:14   ` David Sterba
2015-06-16 17:19     ` Chris Mason [this message]
2015-06-17 13:35       ` Dave Jones
2015-06-30 19:20         ` Dave Jones
2015-06-30 19:23           ` Josef Bacik
2015-06-30 19:28             ` Dave Jones

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=55805A98.9020609@fb.com \
    --to=clm@fb.com \
    --cc=davej@codemonkey.org.uk \
    --cc=dsterba@suse.cz \
    --cc=jbacik@fb.com \
    --cc=linux-kernel@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