diff options
| author | Daniel Vetter <[email protected]> | 2021-02-04 19:45:19 +0100 |
|---|---|---|
| committer | Borislav Petkov <[email protected]> | 2021-02-05 10:45:11 +0100 |
| commit | dc9b7be557ca94301ea5c06c0d72307e642ffb18 (patch) | |
| tree | 67e478e1a6b9cc0c801c633eee8464525f4dcb25 /net/unix/unix_bpf.c | |
| parent | 3ac517313b929619dbb7ceae005ec66d0859b23b (diff) | |
x86/sgx: Drop racy follow_pfn() check
PTE insertion is fundamentally racy, and this check doesn't do anything
useful. Quoting Sean:
"Yeah, it can be whacked. The original, never-upstreamed code asserted
that the resolved PFN matched the PFN being installed by the fault
handler as a sanity check on the SGX driver's EPC management. The
WARN assertion got dropped for whatever reason, leaving that useless
chunk."
Jason stumbled over this as a new user of follow_pfn(), and I'm trying
to get rid of unsafe callers of that function so it can be locked down
further.
This is independent prep work for the referenced patch series:
https://lore.kernel.org/dri-devel/[email protected]/
Fixes: 947c6e11fa43 ("x86/sgx: Add ptrace() support for the SGX driver")
Reported-by: Jason Gunthorpe <[email protected]>
Signed-off-by: Daniel Vetter <[email protected]>
Signed-off-by: Borislav Petkov <[email protected]>
Reviewed-by: Jarkko Sakkinen <[email protected]>
Link: https://lkml.kernel.org/r/[email protected]
Diffstat (limited to 'net/unix/unix_bpf.c')
0 files changed, 0 insertions, 0 deletions