Message ID | 20190227010544.597579-1-jeremy.linton@arm.com |
---|---|
Headers | show |
Series | arm64: add system vulnerability sysfs entries | expand |
Hi Jeremy, On Tue, Feb 26, 2019 at 07:05:34PM -0600, Jeremy Linton wrote: > Jeremy Linton (6): > arm64: Provide a command line to disable spectre_v2 mitigation > arm64: add sysfs vulnerability show for meltdown > arm64: Always enable spectrev2 vulnerability detection > arm64: add sysfs vulnerability show for spectre v2 > arm64: Always enable ssb vulnerability detection > arm64: add sysfs vulnerability show for speculative store bypass > > Marc Zyngier (2): > arm64: Advertise mitigation of Spectre-v2, or lack thereof > arm64: Use firmware to detect CPUs that are not affected by Spectre-v2 > > Mian Yousaf Kaukab (2): > arm64: add sysfs vulnerability show for spectre v1 > arm64: enable generic CPU vulnerabilites support The patches look fine to me (I'm giving them some testing now). However, It would be nice if we got the acks/reviewed-by tags from the people that looked at the previous series (Andre, Suzuki, Julien). You haven't included any tags in this series, I guess there were sufficient changes not to carry them over. If I get the acks by tomorrow, I'll queue them for 5.1, otherwise they'd have to wait for the next merging window. Thanks. -- Catalin
Hi Jeremy, > Jeremy Linton <jeremy.linton@arm.com> hat am 27. Februar 2019 um 02:05 geschrieben: > > > Arm64 machines should be displaying a human readable > vulnerability status to speculative execution attacks in > /sys/devices/system/cpu/vulnerabilities > > This series enables that behavior by providing the expected > functions. Those functions expose the cpu errata and feature > states, as well as whether firmware is responding appropriately > to display the overall machine status. This means that in a > heterogeneous machine we will only claim the machine is mitigated > or safe if we are confident all booted cores are safe or > mitigated. > here are the results for Raspberry Pi 3 B: l1tf:Not affected meltdown:Not affected spec_store_bypass:Not affected spectre_v1:Mitigation: __user pointer sanitization spectre_v2:Not affected Tested-by: Stefan Wahren <stefan.wahren@i2se.com>