On Thu, 22 Feb 2024 at 12:55, Kent Overstreet <kent.overstreet@xxxxxxxxx> wrote: > > On Thu, Feb 22, 2024 at 12:44:17PM +0100, Jan Kara wrote: > > On Thu 22-02-24 06:27:14, Kent Overstreet wrote: > > > My intent is to make a real effort towards getting better interfaces > > > going, prod those maintainers, _then_ look at adding those hacks (that > > > will necessarily be short term solutions since 64 bits is already > > > looking cramped). > > > > OK, fine by me :) So one thing is still not quite clear to me - how do you > > expect the INO_NOT_UNIQUE flag to be used by these apps? Do you expect them > > to use st_dev + st_ino by default and fall back to fsid + fhandle only when > > INO_NOT_UNIQUE is set? > > Shouldn't matter. If they care about performance and they're in some > strange situation where the syscal overhead matters, If it's expensive, then just make the overhead smaller (by adding fh and uuid to statx(2), for example). Using st_ino is also racy in some filesystems, due to the fact that the ino can be reused. If userspace is converted, it should be converted properly, there's just no excuse to add conditional code like that, which makes things more complex and less reliable. Thanks, Miklos
