ntrack does not close netlink socket on exec

Bug #612870 reported by Alexander Sack
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ntrack
Incomplete
Medium
Alexander Sack

Bug Description

when using ntrack in a parent process, a fresh fork gets "permission denied" errors. This happens because the FD_CLOEXEC is not set on the netlink fd.

Alexander Sack (asac)
Changed in ntrack:
status: New → Triaged
importance: Undecided → Medium
milestone: none → 009
Revision history for this message
Alexander Sack (asac) wrote :

gobject part seemed to be ok already; anyway, i added a simple recycle test for it too ...

------------------------------------------------------------
revno: 205
committer: Alexander Sack <email address hidden>
branch nick: ntrack
timestamp: Tue 2010-08-10 22:54:05 +0200
message:
  gobject[test]: add recycle test that verifies that unrefing a gmonitor works
------------------------------------------------------------

Changed in ntrack:
assignee: nobody → Alexander Sack (asac)
status: Triaged → In Progress
Revision history for this message
Alexander Sack (asac) wrote :

oops the comment above was supposed to go to bug 612868

Changed in ntrack:
status: In Progress → Triaged
Revision history for this message
Alexander Sack (asac) wrote :

ATM, I think the right way is to allow apps to poke the netlink socket fd by itself rather than deciding what options are best in the lib.

Revision history for this message
Alexander Sack (asac) wrote :

missed 009 release ... moving to 010

Changed in ntrack:
milestone: 009 → 010
Alexander Sack (asac)
Changed in ntrack:
milestone: 010 → 011
Alexander Sack (asac)
Changed in ntrack:
milestone: 011 → 012
Revision history for this message
Alexander Sack (asac) wrote :

I wonder if this still the case with libnl-2 ... would be great if this is gone just like this ;) ... will report back what my tests show

Alexander Sack (asac)
Changed in ntrack:
milestone: 012 → 013
Alexander Sack (asac)
Changed in ntrack:
milestone: 013 → 014
Revision history for this message
Alexander Sack (asac) wrote :

moving ahead until i have ported my ntrack ffox patch to latest ffox and verified that it isn't broken anymore.

Changed in ntrack:
milestone: 014 → 015
Revision history for this message
Alexander Sack (asac) wrote :

currently cannot reproduce. once i have a new ffox patch i will try again.

Changed in ntrack:
milestone: 015 → none
status: Triaged → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.