Re: PID namespaces break initrd+hibernate combination?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Nigel Cunningham wrote:
Hi all.

Please excuse me if this has already been answered. I'm not currently subscribed to LKML.

I've just been preparing a new tux-on-ice release against Linus' current tree, and encountered a failure to freeze pid 1 when seeking to resume, using an initrd:

[   74.192734] Freezing of tasks failed after 19.99 seconds (1 tasks refusing to freeze):
[   74.193502]   task                        PC stack   pid father
[   74.193504] swapper       S ffff810002023030  4968     1      0
[   74.193512]  ffff81000203fdb0 0000000000000046 ffff810002023040 ffff810003249140
[   74.194296]  ffff81000203fd80 ffffffff803150a1 ffff81000203fdb0 ffff810002023180
[   74.195087]  ffff810002023030 0000000000000004 0000000000000001 0000000000000001
[   74.195860] Call Trace:
[   74.196123]  [<ffffffff803150a1>] security_task_wait+0x11/0x20
[   74.196692]  [<ffffffff802320cd>] do_wait+0x51d/0xda0
[   74.197187]  [<ffffffff802292f0>] default_wake_function+0x0/0x10
[   74.197772]  [<ffffffff8023297c>] sys_wait4+0x2c/0x30
[   74.198264]  [<ffffffff805f4bb5>] initrd_load+0x175/0x370
[   74.198794]  [<ffffffff805f211f>] prepare_namespace+0x8f/0x1d0
[   74.199362]  [<ffffffff805f174d>] kernel_init+0x1ad/0x2b0
[   74.199889]  [<ffffffff8047e526>] _spin_unlock_irq+0x26/0x60
[   74.200439]  [<ffffffff8022afc7>] finish_task_switch+0x67/0xc0
[   74.201008]  [<ffffffff8020c548>] child_rip+0xa/0x12
[   74.201494]  [<ffffffff80364770>] acpi_os_acquire_lock+0x9/0xb
[   74.202063]  [<ffffffff805f15a0>] kernel_init+0x0/0x2b0
[   74.202570]  [<ffffffff8020c53e>] child_rip+0x0/0x12

I believe it might be related to pid namespaces, but am not completely sure yet (will do a git bisect if needs be).
Hmm. prepare_namespace() seems more about mounting root filesystem and less about pid namespace. but I could be wrong. Do you have any more console messages ? CCing the containers list
So, then, I'm writing to ask: Is this a known issue? Is there any fix already available that I've not found in my googling?

Regards,

Nigel


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux