Split from #24588.
The problem here is accurately explained by this comment in std.Build.Fuzz.sendUpdate:
|
// TODO: this isn't sound! We need to do volatile reads of these bits rather than handing the |
|
// buffer off to the kernel, because we might race with the fuzzer process[es]. This brings the |
|
// whole mmap strategy into question. Incidentally, I wonder if post-writergate we could pass |
|
// this data straight to the socket with sendfile... |
To close this issue, the problem explained in that comment must be resolved.
