Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758105AbcCVBQ6 (ORCPT ); Mon, 21 Mar 2016 21:16:58 -0400 Received: from mail-io0-f179.google.com ([209.85.223.179]:34436 "EHLO mail-io0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758026AbcCVBQz (ORCPT ); Mon, 21 Mar 2016 21:16:55 -0400 MIME-Version: 1.0 In-Reply-To: <20160322002436.angclbg3eg6c65ik@floor.thefacebook.com> References: <20160322002436.angclbg3eg6c65ik@floor.thefacebook.com> Date: Mon, 21 Mar 2016 18:16:54 -0700 X-Google-Sender-Auth: eug3SFKoxL2kD4Xp_-lwQl2REwk Message-ID: Subject: Re: [GIT PULL] Btrfs From: Linus Torvalds To: Chris Mason , Linus Torvalds , LKML , linux-btrfs Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 471 Lines: 13 On Mon, Mar 21, 2016 at 5:24 PM, Chris Mason wrote: > > I waited an extra day to send this one out because I hit a crash late > last week with CONFIG_DEBUG_PAGEALLOC enabled (fixed in the top commit). Hmm. If that commit helps, it will spit out a warning. So is it actually fixed, or just hacked around to the point where you don't get a page fault? That WARN_ON_ONCE kind of implies it's a "this happens, but we don't know why". Linus