diff options
author | наб <nabijaczleweli@nabijaczleweli.xyz> | 2023-08-17 22:05:14 +0200 |
---|---|---|
committer | Rich Felker <dalias@aerifal.cx> | 2023-08-19 14:46:20 -0400 |
commit | 7291c6c66a8d033bb487e6d8c8b003c8a7b6a550 (patch) | |
tree | 57ae71aa246bd948d2ae65f22caac009cc8e663e /include/sys/membarrier.h | |
parent | 39e43f0881b12d602ddcb8a9e9295456354b765b (diff) | |
download | musl-7291c6c66a8d033bb487e6d8c8b003c8a7b6a550.tar.gz musl-7291c6c66a8d033bb487e6d8c8b003c8a7b6a550.tar.xz musl-7291c6c66a8d033bb487e6d8c8b003c8a7b6a550.zip |
statvfs: allocate spare for f_type
This is the only missing part in struct statvfs. The LSB calls [f]statfs() deprecated, and its weird types are definitely off-putting. However, its use is required to get f_type. Instead, allocate one of the six spares to f_type, copied directly from struct statfs. This then becomes a small extension to the standard interface on Linux, instead of two different interfaces, one of which is quite odd due to being an ABI type, and there no longer is any reason to use statfs(). The underlying kernel type is a mess, but all architectures agree on u32 (or more) for the ABI, and all filesystem magicks are 32-bit integers. Since commit 6567db65f495cf7c11f5c1e60a3e54543d5a69bc (prior to 1.0.0), the spare slots have been zero-filled, so on all versions that may be reasonably be encountered in the wild, applications can rely on a nonzero f_type as indication that the new field has been filled in.
Diffstat (limited to 'include/sys/membarrier.h')
0 files changed, 0 insertions, 0 deletions