With the help of the static detector I wrote and my long-term research understanding of atomic:ordering, I made fine-grained modifications to the use of atomic::order in the teaclave source code and added relevant comments to address thread performance and security issues caused by sorting in specific processors. You can view, comment on, or merge this pull request online at:
https://github.com/apache/incubator-teaclave-sgx-sdk/pull/447 -- Commit Summary -- * modify ordering -- File Changes -- M samplecode/localattestation/attestation/src/func.rs (11) M sgx_no_tstd/src/lib.rs (11) M sgx_tstd/hashbrown/benches/bench.rs (4) M sgx_tstd/src/alloc.rs (11) M sgx_tstd/src/panic.rs (7) M sgx_tstd/src/panicking.rs (6) M sgx_tstd/src/sync/mpsc/blocking.rs (12) M sgx_tstd/src/sync/mpsc/oneshot.rs (33) M sgx_tstd/src/sync/mpsc/shared.rs (92) M sgx_tstd/src/sync/mpsc/spsc_queue.rs (26) M sgx_tstd/src/sync/mpsc/stream.rs (63) M sgx_tstd/src/sync/mpsc/sync.rs (10) M sgx_tstd/src/thread/scoped.rs (9) -- Patch Links -- https://github.com/apache/incubator-teaclave-sgx-sdk/pull/447.patch https://github.com/apache/incubator-teaclave-sgx-sdk/pull/447.diff -- Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/447 You are receiving this because you are subscribed to this thread. Message ID: <apache/incubator-teaclave-sgx-sdk/pull/4...@github.com>
