diff options
| author | Pat Tullmann <pat.github@tullmann.org> | 2025-07-19 09:34:04 -0700 |
|---|---|---|
| committer | Pat Tullmann <pat.github@tullmann.org> | 2025-08-06 22:12:42 -0700 |
| commit | cf47d283d101e5d8e0d1ca7ec427d40efc40f358 (patch) | |
| tree | 96494f4cd5859c4ba30d375552912c4445f9a2ab /lib/std/http/Client.zig | |
| parent | caf80e90b85a2a7855c369887dce163cf036ff7e (diff) | |
| download | zig-cf47d283d101e5d8e0d1ca7ec427d40efc40f358.tar.gz zig-cf47d283d101e5d8e0d1ca7ec427d40efc40f358.zip | |
lib/std/posix/test.zig: don't compare blksize in "fstatat"
In trying to reproduce the race in #24380, my system tripped over the stat
"blocks" field changing in this test. The value was almost always 8
(effectively 4k) or very infrequently 0 (I saw the 0 from both `fstat` and
`fstatat`). I believe the underlying filesystem is free to asynchronously
change this value. For example, if it migrates a file between some
"inline" or maybe journal storage, and actual on-disk blocks. So it seems
plausible that its allowed to change between stat calls.
Breaking up the struct comparison this way means we also don't compare any
of the padding or "reserved" fields, too. And we can narrow down the
s390x-linux work-around.
Diffstat (limited to 'lib/std/http/Client.zig')
0 files changed, 0 insertions, 0 deletions