summaryrefslogtreecommitdiffhomepage
path: root/third_party/gvsync/memmove_unsafe.go
diff options
context:
space:
mode:
authorMichael Pratt <mpratt@google.com>2019-10-01 12:16:41 -0700
committergVisor bot <gvisor-bot@google.com>2019-10-01 12:25:11 -0700
commit277f84ad20871d1f830a3e63486e8784e8dd3164 (patch)
tree1999cc82b2e1a2584be2a91a66f6356429d7c8e6 /third_party/gvsync/memmove_unsafe.go
parentdd69b49ed1103bab82a6b2ac95221b89b46f3376 (diff)
Support new interpreter requirements in test
Refactoring in 0036d1f7eb95bcc52977f15507f00dd07018e7e2 (v4.10) caused Linux to start unconditionally zeroing the remainder of the last page in the interpreter. Previously it did not due so if filesz == memsz, and *still* does not do so when filesz == memsz for loading binaries, only interpreter. This inconsistency is not worth replicating in gVisor, as it is arguably a bug, but our tests must ensure we create interpreter ELFs compatible with this new requirement. PiperOrigin-RevId: 272266401
Diffstat (limited to 'third_party/gvsync/memmove_unsafe.go')
0 files changed, 0 insertions, 0 deletions