Open Bug 806824 Opened 12 years ago Updated 2 years ago

WebRTC possible data race with nr_ice_ctx_create vs. nr_ice_socket_readable_cb

Categories

(Core :: WebRTC: Networking, defect, P5)

x86
Linux
defect

Tracking

()

People

(Reporter: posidron, Unassigned)

References

Details

(Whiteboard: [tsan] )

Attachments

(1 file)

Attached file callstack
media/mtransport/third_party/nrappkit/src/util/libekr/r_memory.c:85 mem_usage+=CHUNK_SIZE(size); media/mtransport/third_party/nrappkit/src/util/libekr/r_memory.c:116 mem_usage-=CHUNK_SIZE(chunk->size); Tested with m-c changeset: 111684:e19e170d2f6d Marked as s-s because memory functions are involved, please downgrade if necessary.
Whiteboard: [tsan] → [tsan] [WebRTC] [blocking-webrtc+]
This is a legitimate race condition, but the thing that is changing is pure accounting code. I.e., it's just used as part of nrappkit's internal memory statistics subsystem. So I believe this is harmless.
Group: core-security
Whiteboard: [tsan] [WebRTC] [blocking-webrtc+] → [tsan] [WebRTC] [blocking-webrtc-]
Severity: critical → normal
backlog: --- → webRTC+
Rank: 45
Component: WebRTC → WebRTC: Networking
Priority: -- → P4
QA Contact: jsmith
Whiteboard: [tsan] [WebRTC] [blocking-webrtc-] → [tsan]
Mass change P4->P5 to align with new Mozilla triage process.
Priority: P4 → P5
Has Regression Range: --- → irrelevant
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: