[SRU] race condition bringing up interfaces with AppArmor
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ifupdown (Ubuntu) |
Fix Released
|
Undecided
|
Kees Cook | ||
Lucid |
Fix Released
|
Undecided
|
Jamie Strandboge | ||
Maverick |
Fix Released
|
Undecided
|
Jamie Strandboge | ||
Natty |
Fix Released
|
Undecided
|
Kees Cook |
Bug Description
Binary package hint: ifupdown
Due to a missing upstart feature (bug 568860), /etc/init/
network-manger starting
network-
networking starting
networking runs and finishes, bringing up eth0, running dhclient3
network-
...
i.e. since network-manager caused network-
Changed in ifupdown (Ubuntu Natty): | |
assignee: | nobody → Kees Cook (kees) |
summary: |
- race condition bringing up interfaces with AppArmor + [SRU] race condition bringing up interfaces with AppArmor |
Changed in ifupdown (Ubuntu Lucid): | |
assignee: | nobody → Jamie Strandboge (jdstrand) |
Changed in ifupdown (Ubuntu Maverick): | |
assignee: | nobody → Jamie Strandboge (jdstrand) |
Changed in ifupdown (Ubuntu Lucid): | |
status: | Confirmed → Fix Committed |
Changed in ifupdown (Ubuntu Maverick): | |
status: | Confirmed → Fix Committed |
tags: | added: apparmor |
You can trigger this race by adding "sleep 60" to the start of /etc/init. d/apparmor and adding "sleep 20" to the pre-start script in /etc/init/ network- interface- security. conf. The result after boot will be seeing dhclient3 running but not enforced in "sudo aa-status".