4f09782da28d75db8cc49f0a182d15b2c5fec4aa8636b3c6682746e165c7f86ee3a4527c552c53018ed728e61d4d04384748c0e1d668f663928442abdc3f31049c4b35194c4cf34a09bf4195e2e5a5e4f98bd1783902cd5422d7d88c3ce7396cb15137bbec8b036ede2b4cdc4de555f44e7de092e766907cb763b27b3ce1767bc3d5e7bf8ae35b9456d4605ea4094ecba0deaa512a12678"}, 0x1004)
21:31:10 executing program 3:
perf_event_open(0x0, 0x0, 0x0, 0xffffffffffffffff, 0x0)
r0 = openat$sysfs(0xffffffffffffff9c, &(0x7f0000002c80)='/sys/power/pm_trace_dev_match', 0x0, 0x0)
close(r0)
BUG: memory leak
unreferenced object 0x00041640 (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