linux-kernel - Re: filesystem time stamp resolution

lists.openwall.net		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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 26 Feb 2009 19:19:09 -0500
From:	Christoph Hellwig <hch@...radead.org>
To:	Ulrich Drepper <drepper@...hat.com>
Cc:	Al Viro <viro@...IV.linux.org.uk>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: filesystem time stamp resolution

On Thu, Feb 26, 2009 at 03:57:44PM -0800, Ulrich Drepper wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Al Viro wrote:
> > Who said that it's not going to be dependent on the flags used to
> > create and/or mount the filesystem?  IOW, what makes you think that
> > knowing fs type will be enough to derive that data from?
> 
> Nothing.  Just the hope that the sanity of the users is a concern when
> these features are designed.
> 
> Regardless, we need some sort of solution.  I just looked, there is
> spare room in the kstatfs structure.  We could have a value returned in
> a new f_tsres field or so.  That could be per mount point.

Or finally get a pathconf syscall and inode operation..

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/