docker application OOM killed make the kernel crash.

[bugproxy]

== Comment: #0 - Hui Chen <email address hidden> - 2018-08-19 09:38:05 ==
---Problem Description---
docker application OOM killed make the kernel crash.

Contact Information = <email address hidden>

---uname output---
Linux hchenxa-1 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:15:17 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

---Debugger Data---
the kern log like below:
[ 1573.528525] CR2: 0000000000000090 CR3: 000000015c48a003 CR4: 00000000001606e0
[ 1573.529354] Call Trace:
[ 1573.529678] tcp_sk_init+0x2c7/0x320
[ 1573.530133] ops_init+0x44/0x130
[ 1573.530575] ? ida_simple_get+0x98/0x100
[ 1573.531059] setup_net+0x9b/0x150
[ 1573.531499] copy_net_ns+0xd1/0x210
[ 1573.531956] create_new_namespaces+0x11f/0x1d0
[ 1573.532487] unshare_nsproxy_namespaces+0x5e/0xb0
[ 1573.533092] SyS_unshare+0x213/0x3c0
[ 1573.533544] do_syscall_64+0x73/0x130
[ 1573.534006] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[ 1573.534603] RIP: 0033:0x7f92d3a19547
[ 1573.535086] RSP: 002b:00007fff7fede608 EFLAGS: 00000202 ORIG_RAX: 0000000000000110
[ 1573.535946] RAX: ffffffffffffffda RBX: 000056115de6e27c RCX: 00007f92d3a19547
[ 1573.536780] RDX: 0000000000000000 RSI: 000056115d272296 RDI: 000000006c020000
[ 1573.537577] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
[ 1573.538359] R10: 0000000000000006 R11: 0000000000000202 R12: 0000000000000000
[ 1573.539150] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[ 1573.539929] Code: 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 48 8b 87 48 05 00 00 49 89 fc bb ff ff ff ff 49 c7 c5 a0 d9 e5 9f <48> 8b b8 90 00 00 00 e8 60 76 86 ff 89 df 4c 89 ee e8 46 89 0b
[ 1573.542129] RIP: tcp_sk_exit+0x24/0x90 RSP: ffffb1b5caef7d50
[ 1573.542814] CR2: 0000000000000090

and the stack trace like below:
crash> bt
PID: 13988 TASK: ffff8ad4f1548000 CPU: 15 COMMAND: "runc:[1:CHILD]"
 #0 [ffffb1b5caef79a0] machine_kexec at ffffffff9e862873
 #1 [ffffb1b5caef7a00] __crash_kexec at ffffffff9e928f59
 #2 [ffffb1b5caef7ac8] crash_kexec at ffffffff9e929cb1
 #3 [ffffb1b5caef7ae8] oops_end at ffffffff9e830a98
 #4 [ffffb1b5caef7b10] no_context at ffffffff9e872e1c
 #5 [ffffb1b5caef7b78] __bad_area_nosemaphore at ffffffff9e8731d3
 #6 [ffffb1b5caef7bb8] bad_area at ffffffff9e873446
 #7 [ffffb1b5caef7be0] __do_page_fault at ffffffff9e873946
 #8 [ffffb1b5caef7c58] do_page_fault at ffffffff9e873ace
 #9 [ffffb1b5caef7c88] do_async_page_fault at ffffffff9e86a4a1
#10 [ffffb1b5caef7ca0] async_page_fault at ffffffff9f201615
    [exception RIP: tcp_sk_exit+36]
    RIP: ffffffff9f0b91d4 RSP: ffffb1b5caef7d50 RFLAGS: 00010282
    RAX: 0000000000000000 RBX: 00000000ffffffff RCX: 0000000000000006
    RDX: 0000000000000000 RSI: 0000000000000096 RDI: ffff8ad49ec817c0
    RBP: ffffb1b5caef7d68 R8: 0000000000000001 R9: 00000000000030f8
    R10: ffffb1b5caef7c10 R11: 0000000000000000 R12: ffff8ad49ec817c0
    R13: ffffffff9fe5d9a0 R14: ffffb1b5caef7df0 R15: 0000000000000000
    ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018
#11 [ffffb1b5caef7d70] tcp_sk_init at ffffffff9f0ba7a7
#12 [ffffb1b5caef7da8] ops_init at ffffffff9f03ccf4
#13 [ffffb1b5caef7de8] setup_net at ffffffff9f03ce7b
#14 [ffffb1b5caef7e30] copy_net_ns at ffffffff9f03d601
#15 [ffffb1b5caef7e68] create_new_namespaces at ffffffff9e8ad6df
#16 [ffffb1b5caef7ea0] unshare_nsproxy_namespaces at ffffffff9e8ad91e
#17 [ffffb1b5caef7ed0] sys_unshare at ffffffff9e88a803
#18 [ffffb1b5caef7f30] do_syscall_64 at ffffffff9e803ae3
#19 [ffffb1b5caef7f50] entry_SYSCALL_64_after_hwframe at ffffffff9f200081
    RIP: 00007f92d3a19547 RSP: 00007fff7fede608 RFLAGS: 00000202
    RAX: ffffffffffffffda RBX: 000056115de6e27c RCX: 00007f92d3a19547
    RDX: 0000000000000000 RSI: 000056115d272296 RDI: 000000006c020000
    RBP: 0000000000000000 R8: 0000000000000000 R9: 0000000000000000
    R10: 0000000000000006 R11: 0000000000000202 R12: 0000000000000000
    R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
    ORIG_RAX: 0000000000000110 CS: 0033 SS: 002b

Machine Type = x86

---System Hang---
 The machine was rebooted after round of application OOM killed

---Steps to Reproduce---
 Create a docker application and make the application OOM killed by setting resource limits.

*Additional Instructions for <email address hidden>:
-Post a private note with access information to the machine that is currently in the debugger.

[Andrew Cloke (andrew-cloke)]

This bug has been mirrored as a Power issue, but the architecture in the bug report appears to show the issue has occurred on "x86_64".

Could you clarify the hardware and architecture where this issue was seen?

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2018-08-20 05:29 EDT-------
(In reply to comment #4)
> This bug has been mirrored as a Power issue, but the architecture in the bug
> report appears to show the issue has occurred on "x86_64".
>
> Could you clarify the hardware and architecture where this issue was seen?

I saw this issue on x86 machine

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2018-09-19 03:05 EDT-------
Any update on this

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2019-03-15 02:31 EDT-------
Any updates on this?

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2020-06-18 05:00 EDT-------
Hello Canonical,

Any update on this?