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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0E752C6FA8B for ; Thu, 8 Sep 2022 18:22:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231982AbiIHSW5 (ORCPT ); Thu, 8 Sep 2022 14:22:57 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60636 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231908AbiIHSWy (ORCPT ); Thu, 8 Sep 2022 14:22:54 -0400 Received: from fieldses.org (fieldses.org [IPv6:2600:3c00:e000:2f7::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 398B7F10D8; Thu, 8 Sep 2022 11:22:53 -0700 (PDT) Received: by fieldses.org (Postfix, from userid 2815) id 1456B607F; Thu, 8 Sep 2022 14:22:52 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.11.0 fieldses.org 1456B607F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fieldses.org; s=default; t=1662661372; bh=tcd0OCSNWv9F8gta/KRyPIJslgaIHLsZ5kto0SVYY+4=; h=Date:To:Cc:Subject:References:In-Reply-To:From:From; b=HI44ybOnJ4MmTizmstLbVBDNQo1/h12dSOxeF8h+ha7rnqXA24yHaqpYRO6/6Hnya 5/VbgN7+3aX3DCaLHNJpEGw5OlCtoQl/R/3xNY9yB9tnSZ5CFzktzK3u1Kg4S7agy9 6c1ct0ywl/Do7Vh2ie5K8s71iwxNKgOwr870V9E8= Date: Thu, 8 Sep 2022 14:22:52 -0400 To: Jeff Layton Cc: Theodore Ts'o , Jan Kara , NeilBrown , adilger.kernel@dilger.ca, djwong@kernel.org, david@fromorbit.com, trondmy@hammerspace.com, viro@zeniv.linux.org.uk, zohar@linux.ibm.com, xiubli@redhat.com, chuck.lever@oracle.com, lczerner@redhat.com, brauner@kernel.org, fweimer@redhat.com, linux-man@vger.kernel.org, linux-api@vger.kernel.org, linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, ceph-devel@vger.kernel.org, linux-ext4@vger.kernel.org, linux-nfs@vger.kernel.org, linux-xfs@vger.kernel.org Subject: Re: [man-pages RFC PATCH v4] statx, inode: document the new STATX_INO_VERSION field Message-ID: <20220908182252.GA18939@fieldses.org> References: <79aaf122743a295ddab9525d9847ac767a3942aa.camel@kernel.org> <20220907125211.GB17729@fieldses.org> <771650a814ab1ff4dc5473d679936b747d9b6cf5.camel@kernel.org> <20220907135153.qvgibskeuz427abw@quack3> <166259786233.30452.5417306132987966849@noble.neil.brown.name> <20220908083326.3xsanzk7hy3ff4qs@quack3> <02928a8c5718590bea5739b13d6b6ebe66cac577.camel@kernel.org> <20220908155605.GD8951@fieldses.org> <9e06c506fd6b3e3118da0ec24276e85ea3ee45a1.camel@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9e06c506fd6b3e3118da0ec24276e85ea3ee45a1.camel@kernel.org> User-Agent: Mutt/1.5.21 (2010-09-15) From: bfields@fieldses.org (J. Bruce Fields) Precedence: bulk List-ID: X-Mailing-List: linux-xfs@vger.kernel.org On Thu, Sep 08, 2022 at 01:40:11PM -0400, Jeff Layton wrote: > Yeah, ok. That does make some sense. So we would mix this into the > i_version instead of the ctime when it was available. Preferably, we'd > mix that in when we store the i_version rather than adding it afterward. > > Ted, how would we access this? Maybe we could just add a new (generic) > super_block field for this that ext4 (and other filesystems) could > populate at mount time? Couldn't the filesystem just return an ino_version that already includes it? --b.