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-next>] [day] [month] [year] [list]
Date:	Thu, 26 Feb 2009 15:18:04 -0800
From:	Ulrich Drepper <drepper@...hat.com>
To:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: filesystem time stamp resolution

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

How can code at userlevel (e.g., glibc) determine the resolution of the
a filesystem timestamp?

Boundary condition:

- - I cannot create or modify a file since the information must also
  be available for filesystems where the caller has no write permission

- - it has to work going forward (i.e., hardcoding information is no good
  idea)

One acceptable solution (for me) would be to have directories for the
filesystem types under /proc/fs (or /sys/fs) which show this
information.  E.g.:

  /proc/fs/ext4/timestamp-resolution

Measured in nano-seconds or so.

As a bonus have symlinks like

  /proc/fs/ef53 -> /proc/fs/ext4

(i.e., map the superblock magic number to a name.  But I can live with
this missing.)

As a second bonus any help for network filesystems would be good but.

Do I miss anything that is there already?

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

iEYEARECAAYFAkmnIywACgkQ2ijCOnn/RHRSDgCfUep/fJohBr8kI+iuEFbanL5C
oXYAn03tnvPse68ewluvH5qrqJj02AEG
=W6ln
-----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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ