diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2025-05-29 21:13:17 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2025-05-29 21:13:17 -0700 |
commit | bbd9c366bfb2723435e82717ebbb3398f93a1f63 (patch) | |
tree | 297999b399c1ff43699bca22482f93b6509d0145 /scripts/generate_rust_analyzer.py | |
parent | b78f1293f90642ff9809935aa9df7b964e0f17ba (diff) | |
parent | ed16618c380c32c68c06186d0ccbb0d5e0586e59 (diff) |
Merge tag 'x86_sgx_for_6.16-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull Intel software guard extension (SGX) updates from Dave Hansen:
"A couple of x86/sgx changes.
The first one is a no-brainer to use the (simple) SHA-256 library.
For the second one, some folks doing testing noticed that SGX systems
under memory pressure were inducing fatal machine checks at pretty
unnerving rates, despite the SGX code having _some_ awareness of
memory poison.
It turns out that the SGX reclaim path was not checking for poison
_and_ it always accesses memory to copy it around. Make sure that
poisoned pages are not reclaimed"
* tag 'x86_sgx_for_6.16-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
x86/sgx: Prevent attempts to reclaim poisoned pages
x86/sgx: Use SHA-256 library API instead of crypto_shash API
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions