linux-sgx.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
 messages from 2019-06-21 01:49:28 to 2019-07-12 04:17:33 UTC [more...]

[PATCH for_v21 0/2] x86/sgx: Use SRCU and mmu_notifier
 2019-07-12  4:17 UTC  (10+ messages)
` [PATCH for_v21 1/2] x86/sgx: Use SRCU to protect mm_list during reclaim
` [PATCH for_v21 2/2] x86/sgx: Use mmu_notifier.release() instead of per-vma refcounting

[PATCH for_v21] x86/sgx: Return error from driver init if launch control isn't supported
 2019-07-12  4:12 UTC 

[PATCH for_v21] x86/sgx: Provide stub for sgx_drv_init when driver is disabled
 2019-07-12  4:06 UTC 

[PATCH for_v21] x86/vdso: Do not attempt to fixup #DB or #BP exceptions
 2019-07-12  4:00 UTC  (2+ messages)

[PATCH for_v21] x86/sgx: Flush work if and only if the work struct has been init'd
 2019-07-12  3:56 UTC 

[PATCH for_v21] docs: x86/sgx: Add a blurb on basic EPC management to 'kernel internals'
 2019-07-12  3:47 UTC  (2+ messages)

[PATCH for_v21 v2 0/2] x86/sgx: Use SRCU and mmu_notifier
 2019-07-12  3:41 UTC  (3+ messages)
` [PATCH for_v21 v2 1/2] x86/sgx: Use SRCU to protect mm_list during reclaim
` [PATCH for_v21 v2 2/2] x86/sgx: Use mmu_notifier.release() instead of per-vma refcounting

[RFC PATCH v1 0/3] An alternative __vdso_sgx_enter_enclave() to allow enclave/host parameter passing using untrusted stack
 2019-07-12  3:28 UTC  (29+ messages)
` [RFC PATCH v2 "
  ` [RFC PATCH v3 0/3] x86/sgx: Amend vDSO API to allow enclave/host parameter passing on "
  ` [RFC PATCH v3 1/3] selftests/x86: Fixed Makefile for SGX selftest
  ` [RFC PATCH v3 2/3] x86/vdso: Modify __vdso_sgx_enter_enclave() to allow parameter passing on untrusted stack
  ` [RFC PATCH v3 3/3] selftests/x86: Augment SGX selftest to test new __vdso_sgx_enter_enclave() and its callback interface
` [RFC PATCH v2 1/3] selftests/x86: Fixed Makefile for SGX selftest
` [RFC PATCH v2 3/3] selftests/x86: Augment SGX selftest to test new __vdso_sgx_enter_enclave() and its callback interface

Some LSM and SGX remarks before parting of for two weeks
 2019-07-12  3:12 UTC  (2+ messages)

[PATCH for_v21] x86/sgx: Annotate SGX driver init functions with __init
 2019-07-12  2:51 UTC  (2+ messages)

[RFC PATCH v4 00/12] security: x86/sgx: SGX vs. LSM
 2019-07-12  0:08 UTC  (144+ messages)
` [RFC PATCH v4 01/12] x86/sgx: Use mmu_notifier.release() instead of per-vma refcounting
` [RFC PATCH v4 04/12] x86/sgx: Require userspace to define enclave pages' protection bits
` [RFC PATCH v4 05/12] x86/sgx: Enforce noexec filesystem restriction for enclaves
` [RFC PATCH v4 07/12] LSM: x86/sgx: Introduce ->enclave_map() hook for Intel SGX
` [RFC PATCH v4 08/12] security/selinux: Require SGX_MAPWX to map enclave page WX
` [RFC PATCH v4 09/12] LSM: x86/sgx: Introduce ->enclave_load() hook for Intel SGX
` [RFC PATCH v4 10/12] security/selinux: Add enclave_load() implementation
` [RFC PATCH v4 12/12] LSM: x86/sgx: Show line of sight to LSM support SGX2's EAUG
` [RFC PATCH v2 0/3] security/x86/sgx: SGX specific LSM hooks
  ` [RFC PATCH v3 0/4] "
  ` [RFC PATCH v3 1/4] x86/sgx: Add "
  ` [RFC PATCH v3 2/4] x86/64: Call LSM hooks from SGX subsystem/module
  ` [RFC PATCH v3 3/4] X86/sgx: Introduce EMA as a new LSM module
  ` [RFC PATCH v3 4/4] x86/sgx: Implement SGX specific hooks in SELinux
` [RFC PATCH v2 1/3] x86/sgx: Add SGX specific LSM hooks
` [RFC PATCH v2 2/3] x86/sgx: Call LSM hooks from SGX subsystem/module
` [RFC PATCH v2 3/3] x86/sgx: Implement SGX specific hooks in SELinux

[PATCH v20 00/28] Intel SGX1 support
 2019-07-11 22:12 UTC  (8+ messages)
` [PATCH v20 22/28] x86/traps: Attempt to fixup exceptions in vDSO before signaling

[RFC PATCH v3 00/12] security: x86/sgx: SGX vs. LSM, round 3
 2019-07-10 17:25 UTC  (16+ messages)
` [RFC PATCH v3 04/12] x86/sgx: Require userspace to define enclave pages' protection bits
` [RFC PATCH v3 09/12] LSM: x86/sgx: Introduce ->enclave_load() hook for Intel SGX

LSM module for SGX?
 2019-06-27 19:20 UTC  (3+ messages)


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).