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.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 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 B029DC35656 for ; Fri, 21 Feb 2020 16:29:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 91FD920578 for ; Fri, 21 Feb 2020 16:29:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726927AbgBUQ3z (ORCPT ); Fri, 21 Feb 2020 11:29:55 -0500 Received: from verein.lst.de ([213.95.11.211]:56324 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726747AbgBUQ3z (ORCPT ); Fri, 21 Feb 2020 11:29:55 -0500 Received: by verein.lst.de (Postfix, from userid 2407) id CD39968BFE; Fri, 21 Feb 2020 17:29:52 +0100 (CET) Date: Fri, 21 Feb 2020 17:29:52 +0100 From: Christoph Hellwig To: "Darrick J. Wong" Cc: Christoph Hellwig , linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: Re: [PATCH 3/3] xfs: remove the kuid/kgid conversion wrappers Message-ID: <20200221162952.GA9938@lst.de> References: <20200218210020.40846-1-hch@lst.de> <20200218210020.40846-4-hch@lst.de> <20200221012616.GF9506@magnolia> <20200221155450.GA9228@lst.de> <20200221161943.GY9506@magnolia> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200221161943.GY9506@magnolia> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Fri, Feb 21, 2020 at 08:19:43AM -0800, Darrick J. Wong wrote: > Ok, we were doing it wrong. Should this series have fixed that as the > first patch (so that we could push it into old kernels) followed by the > actual icdinode field removal? Maybe I could squeeze that in after patch 1. Before that we'd get weird mismatch, which is how I arrived at the current series. > (Granted nobody seems to have complained...) Right now the use case seems entirely theoretical, but there are multiple series out on fsdevel that aim to change that.