From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from imap.thunk.org ([74.207.234.97]:44560 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751444AbeA3QIh (ORCPT ); Tue, 30 Jan 2018 11:08:37 -0500 Date: Tue, 30 Jan 2018 10:15:43 -0500 From: Theodore Ts'o To: Jeff Layton Cc: Linus Torvalds , open list , "" , Al Viro , xfs , "open list:NFS, SUNRPC, AND..." , linux-btrfs , linux-integrity , Andrew Morton , "linux-ext4@vger.kernel.org" Subject: Re: [GIT PULL] inode->i_version rework for v4.16 Message-ID: <20180130151543.GB8351@thunk.org> References: <1517228795.5965.24.camel@redhat.com> <1517313948.3658.8.camel@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <1517313948.3658.8.camel@redhat.com> Sender: linux-nfs-owner@vger.kernel.org List-ID: On Tue, Jan 30, 2018 at 07:05:48AM -0500, Jeff Layton wrote: > > I want to make sure I understand what's actually broken here thoug. Is > it only broken when the two values are more than 2**63 apart, or is > there something else more fundamentally wrong here? The other problem is that returning a s64 (or a u64) is extremely inefficient on a 32-bit platform. So in general, it's better to avoid returning a 64-bit type unless it's really necessary.... - Ted