Hi All, We've hit a weird error in Fedora using the 3.8-rcX kernels. It seems the mock tool is getting back ENOMEM when doing very simple things that normally just work. The 3.7 kernels on the same userspace work just fine. It seems just running 'mock init -v' is enough to cause the failure.
Because this is the rawhide kernel, we have some debug options enabled. This happens to trigger this error: [ 89.143660] BUG: sleeping function called from invalid context at kernel/nsproxy.c:217 [ 89.143729] in_atomic(): 0, irqs_disabled(): 1, pid: 1329, name: mock [ 89.143776] no locks held by mock/1329. [ 89.143778] irq event stamp: 324562 [ 89.143781] hardirqs last enabled at (324561): [<ffffffff81163a8d>] get_page_from_freelist+0x51d/0x990 [ 89.143791] hardirqs last disabled at (324562): [<ffffffff816daa9d>] _raw_spin_lock_irq+0x1d/0x60 [ 89.143798] softirqs last enabled at (323936): [<ffffffff81070438>] __do_softirq+0x168/0x3d0 [ 89.143804] softirqs last disabled at (323931): [<ffffffff816e587c>] call_softirq+0x1c/0x30 [ 89.143811] Pid: 1329, comm: mock Not tainted 3.8.0-0.rc6.git1.1.fc19.x86_64 #1 [ 89.143814] Call Trace: [ 89.143823] [<ffffffff8109f8d9>] __might_sleep+0x179/0x230 [ 89.143828] [<ffffffff81097887>] switch_task_namespaces+0x27/0x60 [ 89.143833] [<ffffffff810978d0>] exit_task_namespaces+0x10/0x20 [ 89.143839] [<ffffffff81064692>] copy_process.part.22+0xe32/0x1640 [ 89.143844] [<ffffffff81064f95>] do_fork+0xa5/0x450 [ 89.143849] [<ffffffff816db718>] ? retint_swapgs+0x13/0x1b [ 89.143854] [<ffffffff810653c6>] sys_clone+0x16/0x20 [ 89.143859] [<ffffffff816e48b9>] stub_clone+0x69/0x90 [ 89.143864] [<ffffffff816e44d9>] ? system_call_fastpath+0x16/0x1b At first glance it seems copy_io is failing (possibly because get_task_io_context fails), and then the above fallout is printed. The warning seems fairly valid, but I don't think that is the root of the problem. We've seen this as far back as Linux v3.8-rc2-116-g5f243b9 so far. I can still hit it with 3.8-rc6 as well. I'm still trying to see if the ENOMEM hits without the debug options set, and exactly which commit caused it. I just wanted to see if anyone else had seen odd python issues or other things failing with ENOMEM when they shouldn't while I'm off debugging. Thoughts/tips would be appreciated. josh -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
