Intermittent TSAN socketprocess netwerk/test/unit/test_ech_grease.js | data race in memcpy
Categories
(Core :: Networking, defect, P2)
Tracking
()
People
(Reporter: intermittent-bug-filer, Unassigned)
References
(Blocks 2 open bugs)
Details
(4 keywords, Whiteboard: [necko-triaged])
Attachments
(1 file)
50.18 KB,
text/plain
|
Details |
Filed by: rvandermeulen [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=400695175&repo=try
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/F7r4GxYBQYGZ1BtMzgRFVQ/runs/0/artifacts/public/logs/live_backing.log
Only happens in socketprocess mode.
Comment 1•2 years ago
|
||
Context - I'm looking at scheduling socketprocess xpcshell tests on more Linux configurations and this data race is happening in test_ech_grease.js pretty frequently (but not as often as the race in bug 1808235).
Comment 2•2 years ago
|
||
Comment 3•2 years ago
|
||
The "previous write" stack involves setting some SSL integer pref, which the test does in a few places. Users hopefully are not changing their crypto prefs all of the time so it doesn't really seem exploitable. I'll mark it moderate but maybe it could be unhidden.
Dana, it looks like you touched this test last, so this might be of interest. Thanks.
Comment 4•2 years ago
|
||
Yeah, this doesn't seem exploitable to me. The relevant NSS API isn't thread-safe, but it's just enabling or disabling some ciphersuites. We could either make this an NSS problem and add some locks, or we could only touch NSS configuration stuff on the socket thread (which wouldn't be too hard, and is arguably the correct approach anyway).
Updated•2 years ago
|
Comment 5•2 years ago
|
||
FYI, test_ech_grease.js was skipped for the time-being when bug 1808234 landed, so it'll need re-enabling as part of the patch for this bug.
Updated•2 years ago
|
Description
•