From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 893BDC49ED9 for ; Thu, 12 Sep 2019 08:24:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5CAAE20650 for ; Thu, 12 Sep 2019 08:24:15 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="pA0lTVGV" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730184AbfILIYO (ORCPT ); Thu, 12 Sep 2019 04:24:14 -0400 Received: from mail-ua1-f54.google.com ([209.85.222.54]:44017 "EHLO mail-ua1-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730178AbfILIYO (ORCPT ); Thu, 12 Sep 2019 04:24:14 -0400 Received: by mail-ua1-f54.google.com with SMTP id h23so7716439uao.10 for ; Thu, 12 Sep 2019 01:24:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=vvN1oj5Uvd7TKjy6jymfvyrHCREAW1XrjRxV9mG0FNU=; b=pA0lTVGVvS8IG1YNQOZLu4Rt9jNjz+xgwdW4gDpYmym6YFJkzFdkqJdWp84E8oRzph bGq0DZ588gT649eF90CGC3zxwdnU3a8bszlClRXciMbYRS+H/5RM8Zm4QOrwXn6unsGJ p7Op1T+LN5t04GAEpKsfx67pw9XrftoxYYntvBXJAmFb7G3af9eJbcMl3Q/BdHA8OoED WpVgc0nmSWyXnWMXwmavcy5YALT6DDBh49Qyblcgi1Xz16KSjyZt76gTFsyVDC4FZp3/ CvfHAHhTP0SewU86YDMzBkQvXyzRppSpsPUq+A5YLRdfn+e0p7YrPmZn9ygdGWve1w3r 4Q3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=vvN1oj5Uvd7TKjy6jymfvyrHCREAW1XrjRxV9mG0FNU=; b=mbYRza0+3A1CJFYKSBWgqr10PSAzdkDi06R7xUg4Z7jkP6OFu20jGUJ0gA/EdwpVYa liOXhrIAM1xs65WeJ5eslu9zYEnwhnuoDDvqfPMQiF/D0NczVcDoWn4Uh9qldeNAj3Zj 90y2VNoxx5gOhEtD294CbaTdbB/wIXh/mfI+33BsfBnextIdkg+1N4lHIHZ3iXazre2p u7VHdWjnn+QL2pLYmsd1mQ8Awdnnfv6WiIAzJ9fdG52TTKx9O3sQk+kAFJ61C1pf5GsE U1jn6MxG/roe0NB4s41tkd0/pX3laZUEMIHfie/m1jKbRj5SZFW2ySIb+WpC6GaPFbq3 mayQ== X-Gm-Message-State: APjAAAX3g6ZClgdi7ztbZ9cbHcrU3o+CUAn/0btthRW4PahchJ6g2Aro TGYLKkBtfDIugZs4ICeFr27VZhhQe8VaIYca76c= X-Google-Smtp-Source: APXvYqxlJCN/wgc+LJlW3TEt9gIeJ5BKVY6jkJ2ljpTRprGRf/Oiue2SHdnrw+5nR0b3jvANP0sXDpRtleC0m63EFS4= X-Received: by 2002:ab0:602e:: with SMTP id n14mr4863842ual.17.1568276652917; Thu, 12 Sep 2019 01:24:12 -0700 (PDT) MIME-Version: 1.0 References: <11e4e889f903ddad682297c4420faeb0245414cf.camel@scientia.net> In-Reply-To: From: James Harvey Date: Thu, 12 Sep 2019 04:24:00 -0400 Message-ID: Subject: Re: Massive filesystem corruption since kernel 5.2 (ARCH) To: fdmanana@gmail.com Cc: Christoph Anton Mitterer , linux-btrfs , David Sterba Content-Type: text/plain; charset="UTF-8" Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org On Thu, Sep 12, 2019 at 3:51 AM Filipe Manana wrote: > ... > > Until the fix gets merged to 5.2 kernels (and 5.3), I don't really > recommend running 5.2 or 5.3. What is your recommendation for distributions that have been shipping 5.2.x for quite some time, where a distro-wide downgrade to 5.1.x isn't really an option that will be considered, especially because many users aren't using BTRFS? Can/should your patch be backported to 5.2.13/5.2.14? Or, does it really need to be applied to 5.3rc or git master? Or, is it possibly not the right fix for the corruption risk, and should a flashing neon sign be given to users to just run 5.1.x even though the distribution repos have 5.2.x? What is your recommendation for users who have been running 5.2.x and running into a lot of hangs? Would you say to apply your patch to a custom-compiled kernel, or to downgrade to 5.1.x?