lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 27 Apr 2012 00:33:06 +0000
From:	"Myklebust, Trond" <>
To:	Roland McGrath <>
CC:	David Howells <>,
	Steve French <>,
	"" <>,
	"" <>,
	"" <>,
	"" <>,
	"" <>,
	"" <>,
	"" <>,
	"" <>,
	"" <>,
	"" <>
Subject: Re: [PATCH 0/6] Extended file stat system call

On Thu, 2012-04-26 at 15:05 -0700, Roland McGrath wrote:
> > What if the xstat() and struct xstat eventually becomes what userspace
> > uses as stat() (as a wrapper) and struct stat (if such a thing is
> > possible with glibc versioning)?  
> It's certainly possible with symbol versioning, though it seems much more
> likely that we'd stick with the existing struct stat and stat* interfaces
> and only have the implementation using statx underneath (e.g. for new
> machines or kernel ABIs where the kernel stops providing any calls except
> for statxat), at least for the foreseeable future.
> > Do older programs that think they're using stat() and don't know about
> > the extra fields available expect to see a useful value in st_ino?
> POSIX requires that st_ino have a useful value for the standard *stat calls.

Yes, but we're talking about non-POSIX filesystems here. If the
filesystem doesn't have a useful value for st_ino, then the usual way of
dealing with those POSIX requirements is to fake up values. The question
then becomes whether or not we care if it is the kernel or userland that
fakes up those values.

Trond Myklebust
Linux NFS client maintainer


Powered by blists - more mailing lists