syzbot


memory leak in __memcg_init_list_lru_node

Status: fixed on 2019/07/10 21:40
Subsystems: mm
[Documentation on labels]
Fix commit: 3510955b3271 mm/list_lru.c: fix memory leak in __memcg_init_list_lru_node
First crash: 1824d, last: 1810d
Discussions (6)
Title Replies (including bot) Last reply
[PATCH 4.9 000/117] 4.9.183-stable review 121 (121) 2019/06/22 00:44
[PATCH 4.4 00/84] 4.4.183-stable review 88 (88) 2019/06/22 00:43
[PATCH 4.19 00/75] 4.19.53-stable review 83 (83) 2019/06/20 01:46
[PATCH 4.14 00/53] 4.14.128-stable review 62 (62) 2019/06/19 13:40
[PATCH 5.1 000/115] 5.1.12-stable review 132 (132) 2019/06/19 12:16
[PATCH] list_lru: fix memory leak in __memcg_init_list_lru_node 4 (4) 2019/05/28 08:34

Sample crash report:
ffffffffda RBX: 0000000000000003 RCX: 0000000000441f29
BUG: memory leak
unreferenced object 0xffff888121c0cd80 (size 32):
  comm "syz-executor121", pid 7072, jiffies 4294946249 (age 13.290s)
  hex dump (first 32 bytes):
    80 cd c0 21 81 88 ff ff 80 cd c0 21 81 88 ff ff  ...!.......!....
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [<00000000e7b58a4a>] kmemleak_alloc_recursive include/linux/kmemleak.h:43 [inline]
    [<00000000e7b58a4a>] slab_post_alloc_hook mm/slab.h:439 [inline]
    [<00000000e7b58a4a>] slab_alloc mm/slab.c:3326 [inline]
    [<00000000e7b58a4a>] kmem_cache_alloc_trace+0x13d/0x280 mm/slab.c:3553
    [<0000000077bed25b>] kmalloc include/linux/slab.h:547 [inline]
    [<0000000077bed25b>] __memcg_init_list_lru_node+0x58/0xf0 mm/list_lru.c:348
    [<000000009de81f81>] memcg_init_list_lru_node mm/list_lru.c:371 [inline]
    [<000000009de81f81>] memcg_init_list_lru mm/list_lru.c:457 [inline]
    [<000000009de81f81>] __list_lru_init+0x198/0x2a0 mm/list_lru.c:624
    [<00000000a5189e23>] alloc_super+0x2e0/0x310 fs/super.c:269
    [<000000007acd139d>] sget_userns+0x94/0x2a0 fs/super.c:609
    [<00000000fb37ae2c>] sget+0x8d/0xb0 fs/super.c:660
    [<00000000bf79e12f>] mount_bdev+0xa9/0x210 fs/super.c:1319
    [<00000000806721e0>] fuse_mount_blk+0x35/0x40 fs/fuse/inode.c:1275
    [<00000000d462bdb4>] legacy_get_tree+0x27/0x80 fs/fs_context.c:661
    [<0000000084c69d3c>] vfs_get_tree+0x2e/0x120 fs/super.c:1476
    [<000000001590158f>] do_new_mount fs/namespace.c:2790 [inline]
    [<000000001590158f>] do_mount+0x932/0xc50 fs/namespace.c:3110
    [<000000001a375261>] ksys_mount+0xab/0x120 fs/namespace.c:3319
    [<0000000006b6df64>] __do_sys_mount fs/namespace.c:3333 [inline]
    [<0000000006b6df64>] __se_sys_mount fs/namespace.c:3330 [inline]
    [<0000000006b6df64>] __x64_sys_mount+0x26/0x30 fs/namespace.c:3330
    [<00000000271f6a0e>] do_syscall_64+0x76/0x1a0 arch/x86/entry/common.c:301
    [<0000000046d5ad41>] entry_SYSCALL_64_after_hwframe+0x44/0xa9


Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2019/06/10 07:04 upstream d1fdb6d8f6a4 0159583c .config console log report syz C ci-upstream-gce-leak
2019/05/28 12:12 upstream cd6c84d8f0cd 6bd61501 .config console log report syz C ci-upstream-gce-leak
2019/05/26 20:47 upstream 35efb51eee22 85c57315 .config console log report syz C ci-upstream-gce-leak
* Struck through repros no longer work on HEAD.