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=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=ham 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 1B486C169C4 for ; Fri, 8 Feb 2019 21:51:04 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E034221908 for ; Fri, 8 Feb 2019 21:51:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1549662664; bh=pWHwc1cOA0fR2GNK1O9h8EZb6lIcYGF2CAmElqGNrwE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=YqoniCrrATKWY+1LDglqYZofeoaMgi+kcVEyf7QW0X+Mc6+uTE7TaF6Lbs4/V1JlU /l43Ef+LaAY9b+MhjeQ9iicz2bG46j2ukzIpYPPOoL9wIq98NGdtemMXAI+hE/bntr 6+3IV+hBPJRNKr0oW0g8TzRFxrYNGFmgKuMUZn0c= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727003AbfBHVvD (ORCPT ); Fri, 8 Feb 2019 16:51:03 -0500 Received: from mail-pg1-f195.google.com ([209.85.215.195]:36247 "EHLO mail-pg1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726244AbfBHVvD (ORCPT ); Fri, 8 Feb 2019 16:51:03 -0500 Received: by mail-pg1-f195.google.com with SMTP id n2so2158001pgm.3; Fri, 08 Feb 2019 13:51:02 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=8ea58Fje7xTPgTcfyWJ2GK63U/3ne1HaL4GgglbOGD4=; b=HDuH/uiqO6nr6Kp+F8ioPMTjoXPzM4IC2ORnwvd6BvHe1HrbNOKdK+NsVOu43cNqL7 MWWhm2rXcrpJNxygy1kq5Qr0KNsyHRiq2rubg0oBy2vf1D6Y3X0UOx4sysySF7NAstlQ SEQ7lYcqSeRwg0bZMBm85mteMsExkY64o0q905Nw6pboPXuEwW0kJDS+fHo3bZuhPbmr 7fLCfEfasuPKWFz0l6GC1Lu784l1SfGAn/aJLUuqWdOzzPkVUsg8vOE5OYZwru2d7EFv tBt9KI/3t/BUfm4huRqjYYcxfqK/X5sT8mxLBos7kn14cHspxuRf5MFKsUAx0WOolDpQ dU0w== X-Gm-Message-State: AHQUAubZ9l5gW9CEFnRRcz97i2iNcw1o5XPyfPFH/gOi+fH8/fYzdPtA h3wMWXJNyiemRSox3g0a7cpmdFnrCJ8= X-Google-Smtp-Source: AHgI3IbDHf1vnfxA2F2tg9Ipob9xe+ir51wD1om1BSE/pj62kahusly13J0AVwAi2DQkIReqyh9CzQ== X-Received: by 2002:a63:4b5e:: with SMTP id k30mr8576991pgl.212.1549662661904; Fri, 08 Feb 2019 13:51:01 -0800 (PST) Received: from garbanzo.do-not-panic.com (c-73-71-40-85.hsd1.ca.comcast.net. [73.71.40.85]) by smtp.gmail.com with ESMTPSA id j197sm8690799pgc.76.2019.02.08.13.50.59 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 08 Feb 2019 13:51:00 -0800 (PST) Received: by garbanzo.do-not-panic.com (sSMTP sendmail emulation); Fri, 08 Feb 2019 13:50:57 -0800 Date: Fri, 8 Feb 2019 13:50:57 -0800 From: Luis Chamberlain To: Dave Chinner Cc: linux-xfs@vger.kernel.org, gregkh@linuxfoundation.org, Alexander.Levin@microsoft.com, stable@vger.kernel.org, amir73il@gmail.com, hch@infradead.org Subject: Re: [PATCH v2 00/10] xfs: stable fixes for v4.19.y Message-ID: <20190208215057.GL11489@garbanzo.do-not-panic.com> References: <20190204165427.23607-1-mcgrof@kernel.org> <20190205220655.GF14116@dastard> <20190208194829.GJ11489@garbanzo.do-not-panic.com> <20190208213201.GP14116@dastard> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190208213201.GP14116@dastard> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Sat, Feb 09, 2019 at 08:32:01AM +1100, Dave Chinner wrote: > On Fri, Feb 08, 2019 at 11:48:29AM -0800, Luis Chamberlain wrote: > > On Wed, Feb 06, 2019 at 09:06:55AM +1100, Dave Chinner wrote: > > > On Mon, Feb 04, 2019 at 08:54:17AM -0800, Luis Chamberlain wrote: > > > > Kernel stable team, > > > > > > > > here is a v2 respin of my XFS stable patches for v4.19.y. The only > > > > change in this series is adding the upstream commit to the commit log, > > > > and I've now also Cc'd stable@vger.kernel.org as well. No other issues > > > > were spotted or raised with this series. > > > > > > > > Reviews, questions, or rants are greatly appreciated. > > > > > > Test results? > > > > > > The set of changes look fine themselves, but as always, the proof is > > > in the testing... > > > > I've first established a baseline for v4.19.18 with fstests using > > a series of different sections to test against. I annotated the > > failures on an expunge list and then use that expunge list to confirm > > no regressions -- no failures if we skip the failures already known for > > v4.19.18. > > > > Each different configuration I test against I use a section for. I only > > test x86_64 for now but am starting to create a baseline for ppc64le. > > > > The sections I use: > > > > * xfs > > * xfs_nocrc > > * xfs_nocrc_512 > > * xfs_reflink > > * xfs_reflink_1024 > > * xfs_logdev > > * xfs_realtimedev > > Yup, that seems to cover most common things :) To be clear in the future I hope to also have a baseline for: * xfs_bigblock But that is *currently* [0] only possible on the following architectures with the respective kernel config: aarch64: CONFIG_ARM64_64K_PAGES=y ppc64le: CONFIG_PPC_64K_PAGES=y [0] Someone is working on 64k pages on x86 I think? Luis