clone() hang when creating new network namespace (dmesg show unregister_netdevice: waiting for lo to become free. Usage count = 2)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Confirmed
|
High
|
|||
linux (Ubuntu) |
Fix Released
|
High
|
Stefan Bader | ||
Precise |
Fix Released
|
Medium
|
Chris J Arges | ||
Quantal |
Fix Released
|
High
|
Stefan Bader |
Bug Description
SRU Justification:
Impact:
When creating new network namespace dmesg can show the following
unregister_
Fix:
Stefan Bader's SAUCE patch has fixed this for Quantal:
UBUNTU: SAUCE: net/ipv4: Always flush route cache on unregister batch call
Testcase:
The sourcecode found here:
https:/
can be compiled and run as follows:
sudo ./reproducer
#ctrl+c
sudo ./reproducer
#wait for a while
dmesg | grep unregister
--
I'm not sure how I triggered this. I've been moving around between networks and suspending/resuming all day.
Earlier in this boot I successfully used a container (start, networking and stop). I came to start the same one later and noticed that it didn't come up. Trying to attach to the console with lxc-console informed me that it wasn't running. I then saw suspicious content in dmesg:
[25800.412234] INFO: task lxc-start:25817 blocked for more than 120 seconds.
[25800.412243] "echo 0 > /proc/sys/
[25800.412254] lxc-start D ffff88013fd13980 0 25817 1 0x00000000
[25800.412266] ffff880007b43cc0 0000000000000086 ffff88003ba4c500 ffff880007b43fd8
[25800.412275] ffff880007b43fd8 ffff880007b43fd8 ffff880134c65c00 ffff88003ba4c500
[25800.412284] 000080d0ffffffff ffffffff81ca7c00 ffff88003ba4c500 ffffffff81ca7c04
[25800.412288] Call Trace:
[25800.412306] [<ffffffff81673
[25800.412313] [<ffffffff81673
[25800.412323] [<ffffffff81672
[25800.412331] [<ffffffff81672
[25800.412340] [<ffffffff8155e
[25800.412350] [<ffffffff8107a
[25800.412357] [<ffffffff8107a
[25800.412367] [<ffffffff81050
[25800.412375] [<ffffffff81050
[25800.412385] [<ffffffff8116d
[25800.412395] [<ffffffff8118c
[25800.412402] [<ffffffff81181
[25800.412410] [<ffffffff8101c
[25800.412418] [<ffffffff8167c
[25800.412424] [<ffffffff8167c
[25806.312385] unregister_
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-generic 3.5.0.3.3
ProcVersionSign
Uname: Linux 3.5.0-2-generic x86_64
NonfreeKernelMo
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.2.5-0ubuntu2
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: NVidia [HDA NVidia], device 0: Cirrus Analog [Cirrus Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0xd3480000 irq 22'
Mixer name : 'Nvidia MCP89 HDMI'
Components : 'HDA:10134206,
Controls : 37
Simple ctrls : 13
Date: Thu Jul 5 21:26:08 2012
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100729)
MachineType: Apple Inc. MacBookPro7,1
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.82
SourcePackage: linux
UpgradeStatus: Upgraded to quantal on 2012-01-13 (173 days ago)
dmi.bios.date: 03/25/10
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP71.88Z.
dmi.board.name: Mac-F222BEC8
dmi.board.vendor: Apple Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAppleInc
dmi.product.name: MacBookPro7,1
dmi.product.
dmi.sys.vendor: Apple Inc.
summary: |
- lxc-start sometimes stops starting containers + 'stuck on mutex_lock creating a new network namespace when starting a + container |
summary: |
- 'stuck on mutex_lock creating a new network namespace when starting a + stuck on mutex_lock creating a new network namespace when starting a container |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
tags: | added: kernel-da-key kernel-key |
Changed in linux (Ubuntu Quantal): | |
milestone: | none → ubuntu-12.10-beta-2 |
tags: | removed: rls-q-incoming |
tags: | added: patch |
Changed in linux: | |
importance: | Unknown → High |
status: | Unknown → Confirmed |
Changed in linux (Ubuntu Quantal): | |
milestone: | ubuntu-12.10-beta-2 → ubuntu-12.10 |
Changed in linux (Ubuntu Quantal): | |
status: | Triaged → Fix Committed |
tags: | removed: kernel-key |
Changed in linux (Ubuntu Precise): | |
assignee: | nobody → Chris J Arges (arges) |
importance: | Undecided → Medium |
status: | New → In Progress |
description: | updated |
description: | updated |
Changed in linux (Ubuntu Precise): | |
status: | In Progress → Fix Committed |
Can you tell us how to reproduce this issue?
From the dmesg kernel warning opps, I think it is not lxc/cgroups specific issue. Looks like lxc-start was blocked by some stuff for a long time. Is there any heavy workload on your system?
Thanks,
-Bryan