Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 84DAAC636CC for ; Wed, 8 Feb 2023 08:06:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230448AbjBHIGx (ORCPT ); Wed, 8 Feb 2023 03:06:53 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49110 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230366AbjBHIGu (ORCPT ); Wed, 8 Feb 2023 03:06:50 -0500 Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 18B3F6A4C for ; Wed, 8 Feb 2023 00:06:48 -0800 (PST) Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 6A4903200564; Wed, 8 Feb 2023 03:06:45 -0500 (EST) Received: from imap51 ([10.202.2.101]) by compute6.internal (MEProxy); Wed, 08 Feb 2023 03:06:46 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arndb.de; h=cc :cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm3; t=1675843605; x=1675930005; bh=5yKWBSh3Gk Z49uSSSGKd13vlZdjjf2xcz3rZbXFJUj8=; b=MLxSEVnKTtpNhJy4s4Z6SwWrLd M2GPzQY2cs32HhsL1CI+Rn5MJ06oRCFyhJCyNSMCAlSQE+tBlVnHEhZFv9ka0Ra2 Cb8h+DBPRJ2jEv/s/OIt4cc0qBnw5RxgssRmX8Xr7Aa3MfbP5UWTShzt5yDdVyGk nV3J6/5G+s9mwZM4CMNychTKVRL/6DOT4u0ar4RAEgKadOjsmQSQTgb1InzxTGcn rt2MbIKglx8mGOR68IwVDo7cizMjN1kfTvqJYmKRL7uGAwruWYQbDFYk4EKShZ3+ iDQ/DbPZEnXWiPSkhNss+0rWcGoJ37AZ4xVNAaszz2FkjrF5p7vyiwUnsvzA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1675843605; x=1675930005; bh=5yKWBSh3GkZ49uSSSGKd13vlZdjj f2xcz3rZbXFJUj8=; b=srC9EyasVIJ7OP17Anr255vbCOCPRXgQWeMzUk8cQZTe dOT6bMhjai9QQh+CTNNSy6wonmO8Ev/2FOSe1vHGtIsOpAp/TVmL0xFBhIXR73UC xid35edw4yQsWGvcCJB73qc+ZW8ZHK8/W2u1NjBuMW2g+NhjhEJJNSnIBxpqe7yn saO6Y5pj0Rv9XTOmllbbpazat+MVgC1sYRUKCZRD5QWOxxTLkljjSvVzkwEBSXMr vlTZv0hXW0Z+lY+g7pVEB28E8z1HwIhtneYqfOqS14QG4xC78fQpKCphmckpS7zk QHOCQ2k8OIHEJXhR+N86gxsTff0Fiq++EjH+DxLaTg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudegledguddufecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefofgggkfgjfhffhffvvefutgesthdtredtreertdenucfhrhhomhepfdet rhhnugcuuegvrhhgmhgrnhhnfdcuoegrrhhnugesrghrnhgusgdruggvqeenucggtffrrg htthgvrhhnpeffheeugeetiefhgeethfejgfdtuefggeejleehjeeutefhfeeggefhkedt keetffenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe grrhhnugesrghrnhgusgdruggv X-ME-Proxy: Feedback-ID: i56a14606:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 80D4FB60086; Wed, 8 Feb 2023 03:06:44 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.9.0-alpha0-156-g081acc5ed5-fm-20230206.001-g081acc5e Mime-Version: 1.0 Message-Id: <7c98aac5-6b64-4f6b-b242-7ad3b8a334a8@app.fastmail.com> In-Reply-To: References: <1af05c1441e9f96870be1cc20b1162e3f5043b2e.1675734681.git.chenfeiyang@loongson.cn> <1e7da4e7-392d-4a9e-aa95-0599a0c84419@app.fastmail.com> Date: Wed, 08 Feb 2023 09:06:24 +0100 From: "Arnd Bergmann" To: "chris.chenfeiyang" , "Willy Tarreau" Cc: "Paul E. McKenney" , "Feiyang Chen" , "Huacai Chen" , "Jiaxun Yang" , loongarch@lists.linux.dev, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/3] nolibc: Add statx() support to implement sys_stat() Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 8, 2023, at 08:42, Feiyang Chen wrote: > On Wed, 8 Feb 2023 at 11:31, Willy Tarreau wrote: >> >> I generally agree with the Arnd's points overall and I'm fine with the >> rest of your series. On this specific point, I'm fine with your proposal, >> let's just start with sys_statx() only on this arch, please add a comment >> about this possibility in the commit message that brings statx(), >> indicating that other archs are likely to benefit from it as well, and >> let's see after this if we can migrate all archs to statx. >> > > We have a problem if we just start with sys_statx() only on this arch. > When struct stat is not defined, what should we do with stat() in the > nolibc selftest? To clarify: your proposed implementation of the stat() function that fills the nolibc 'struct stat' based on information from 'struct statx' is fine here. Just remove the 'struct sys_stat_struct' definition loongarch but keep 'struct stat'. Arnd