netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: <netdev@vger.kernel.org>
Subject: Re: crash in __kfree_skb on v3.18-rc5 with CONFIG_DEBUG_PAGEALLOC
Date: Fri, 21 Nov 2014 11:33:33 -0500	[thread overview]
Message-ID: <1416587613.24312.4@mail.thefacebook.com> (raw)
In-Reply-To: <20141121160937.GA32608@ret.masoncoding.com>



On Fri, Nov 21, 2014 at 11:16 AM, Chris Mason <clm@fb.com> wrote:
> Hi everyone,
> 
> I've hit this a few times today while hammering on my btrfs queue for
> the next merge window.  It's plain v3.18-rc5 plus a few btrfs patches,
> so it isn't impossible a btrfs double free is causing trouble.

Looking through my console logs, I also hit it on v3.18-rc3 and on a 
test in the middle of the 3.18 merge window (don't have the exact sha, 
sorry).

-chris

      parent reply	other threads:[~2014-11-21 16:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21 16:16 crash in __kfree_skb on v3.18-rc5 with CONFIG_DEBUG_PAGEALLOC Chris Mason
2014-11-21 16:31 ` Eric Dumazet
2014-11-21 16:37   ` Eric Dumazet
2014-11-21 16:47     ` Chris Mason
2014-11-21 16:56       ` Eric Dumazet
2014-11-21 17:18         ` Chris Mason
2014-11-21 16:41   ` Chris Mason
2014-11-21 16:57   ` Chris Mason
2014-11-21 17:04   ` [PATCH net] net: Revert "net: avoid one atomic operation in skb_clone()" Eric Dumazet
2014-11-21 18:05     ` Sabrina Dubroca
2014-11-21 19:29       ` Eric Dumazet
2014-11-21 19:39         ` Chris Mason
2014-11-21 19:47         ` [PATCH v2 " Eric Dumazet
2014-11-21 20:27           ` David Miller
2014-11-21 21:15           ` Chris Mason
2014-11-21 16:33 ` Chris Mason [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=1416587613.24312.4@mail.thefacebook.com \
    --to=clm@fb.com \
    --cc=netdev@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).