98ec1e7e6699bf6a1047144f6f373b7e20a6974438edec6e1d7467b80912d908fa09b23866736330c447e0d9d6027e540ffce4741766ed551e089ed03a4d90fcf048ddc4df8a9d4c436c282b3ba9b7857cf20db7d5ac544c8b129d667e5ccf2e2af47284a6a6ea7a8c8b32cd5b59a234fb2023e11df120dcbc95953b90182f3e175031773af37e8dbb4ac7baea94c6dad19", 0xf4, 0x600000}, &(0x7f0000000180))
timerfd_create(0x4, 0x0)
BUG: memory leak
unreferenced object 0x00041600 (size 48):
  comm "swapper/0", pid 0, jiffies 4294667296
  hex dump (first 32 bytes on cpu 1):
    14 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 0):
    pcpu_alloc_noprof+0x777/0x11b0
    setup_per_cpu_pageset+0x158/0x1f0
    start_kernel+0x34c/0x540
    x86_64_start_reservations+0x18/0x30
    x86_64_start_kernel+0xcb/0xe0
    common_startup_64+0x12c/0x138

BUG: leak checking failed