[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180130151543.GB8351@thunk.org>
Date: Tue, 30 Jan 2018 10:15:43 -0500
From: Theodore Ts'o <tytso@....edu>
To: Jeff Layton <jlayton@...hat.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
open list <linux-kernel@...r.kernel.org>,
"<linux-fsdevel@...r.kernel.org>" <linux-fsdevel@...r.kernel.org>,
Al Viro <viro@...iv.linux.org.uk>,
xfs <linux-xfs@...r.kernel.org>,
"open list:NFS, SUNRPC, AND..." <linux-nfs@...r.kernel.org>,
linux-btrfs <linux-btrfs@...r.kernel.org>,
linux-integrity <linux-integrity@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: [GIT PULL] inode->i_version rework for v4.16
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
Powered by blists - more mailing lists