Mir

fd reception code is not exeception-safe when unexpected numbers of fds are received

Bug #1394362 reported by Kevin DuBois on 2014-11-19
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Low
Kevin DuBois
mir (Ubuntu)
Low
Unassigned

Bug Description

the easiest way to see this is to inspect mir::receive_data, or to run valgrind with track-fds = yes

In the wild, this would only leak 1-4 fd's per error. Given the type of errors that would cause this, it would take a lot of rare errors before we hit the process fd limit.

Related branches

Kevin DuBois (kdub) wrote :
Changed in mir:
milestone: none → 0.10.0
status: New → In Progress
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.10.0

Changed in mir:
status: In Progress → Fix Committed
Changed in mir:
status: Fix Committed → Fix Released
Daniel van Vugt (vanvugt) wrote :

mir (0.10.0+15.04.20150107.2-0ubuntu1) vivid; urgency=medium

Changed in mir (Ubuntu):
importance: Undecided → Low
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Bug attachments