On Tue, May 10, 2016 at 09:25:55AM +0100, David Howells wrote: > Because it's not necessarily a perfectly working version of it. See the Y2037 > problem for example. > > I was assuming that C libraries might want to update the struct stat and the > stat call() to provide fields that aren't currently there in Linux but are in > other OS's. We could even dispense with older stat syscalls on new arches. Please stop this whole let's get rid of old syscalls on new architectures stuff. This just means we have to do the translation multiple, and the one in userspace is more costly as we it needs to be in every copy of the library. And times where we had a single libc instance (nevermind implementation) are long over if we ever actually had them. > However, if we're going to discard this possibility, we can make these > features available only to direct calls of extended stat. And even if we want to to do a stat emulation despite that above argument let's add the flag once a major libc implementation actually wants to use it and taylor it towards the use case. Don't just add it just because, and even more importantly don't make it the default. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
