summaryrefslogtreecommitdiffstats
path: root/usr.bin/tmux/cmd-source-file.c
diff options
context:
space:
mode:
authorderaadt <deraadt@openbsd.org>2019-12-17 22:25:56 +0000
committerderaadt <deraadt@openbsd.org>2019-12-17 22:25:56 +0000
commit3a08873ece1cb28ace89fd65e8f3c1375cc98de2 (patch)
treeff0892ed76043b38c990bd0f7f4460d137613bed /usr.bin/tmux/cmd-source-file.c
parent"allow instance {...}" requires options (diff)
downloadwireguard-openbsd-3a08873ece1cb28ace89fd65e8f3c1375cc98de2.tar.xz
wireguard-openbsd-3a08873ece1cb28ace89fd65e8f3c1375cc98de2.zip
arm64 cpus speculatively execute instructions after ERET, and on some
processors not all microarchitectural side effects are abandoned, leading to spectre-like effects. This was fixed quietly and without responsible disclosure by ARM in linux mainline a year ago, but rediscovered independently by Anthony Steinhauser. ok patrick guenther kettenis comment to ARM: "Responsible Disclosure" doesn't mean "downplay at maximum to avoid damage to the bottom line", the responsibility aspect entails ensuring "all customers are aware of the defect". What happened here is indistinguishable from Intel's behaviour, and that's not the look you want.
Diffstat (limited to 'usr.bin/tmux/cmd-source-file.c')
0 files changed, 0 insertions, 0 deletions