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]

Message-ID: <49A72C78.1060306@redhat.com>
Date:	Thu, 26 Feb 2009 15:57:44 -0800
From:	Ulrich Drepper <drepper@...hat.com>
To:	Al Viro <viro@...IV.linux.org.uk>
CC:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: filesystem time stamp resolution

-----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.

- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEUEARECAAYFAkmnLHgACgkQ2ijCOnn/RHT3FQCgnLHOPL/yItK0D7gZJv93EU0U
Dr0AmNTd35JdveTPHZ8tDUUfiltscoc=
=qIcS
-----END PGP SIGNATURE-----
--
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/