syzbot


memory leak in nfs_fs_context_parse_monolithic

Status: fixed on 2020/04/15 17:19
Subsystems: nfs
[Documentation on labels]
Reported-by: syzbot+193c375dcddb4f345091@syzkaller.appspotmail.com
Fix commit: 75a9b9176157 NFS: Fix leak of ctx->nfs_server.hostname
First crash: 1582d, last: 1554d
Discussions (1)
Title Replies (including bot) Last reply
memory leak in nfs_fs_context_parse_monolithic 0 (1) 2020/02/14 17:37

Sample crash report:
executing program
executing program
BUG: memory leak
unreferenced object 0xffff88811ab4f800 (size 32):
  comm "syz-executor510", pid 7125, jiffies 4294945638 (age 12.830s)
  hex dump (first 32 bytes):
    00 66 73 00 00 00 00 00 00 00 00 00 00 00 00 00  .fs.............
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [<000000008f714c5c>] kstrdup+0x36/0x70 mm/util.c:60
    [<000000009952a8cc>] nfs23_parse_monolithic fs/nfs/fs_context.c:958 [inline]
    [<000000009952a8cc>] nfs_fs_context_parse_monolithic+0x5cf/0x8f0 fs/nfs/fs_context.c:1147
    [<00000000a3a27d9f>] do_new_mount fs/namespace.c:2818 [inline]
    [<00000000a3a27d9f>] do_mount+0x927/0xc50 fs/namespace.c:3107
    [<00000000924f3ed4>] __do_sys_mount fs/namespace.c:3316 [inline]
    [<00000000924f3ed4>] __se_sys_mount fs/namespace.c:3293 [inline]
    [<00000000924f3ed4>] __x64_sys_mount+0xb0/0x120 fs/namespace.c:3293
    [<00000000b3751c4c>] do_syscall_64+0x6e/0x220 arch/x86/entry/common.c:294
    [<00000000c1f5f40a>] entry_SYSCALL_64_after_hwframe+0x44/0xa9


Crashes (18):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/03/12 06:33 upstream f35111a94654 e7caca8e .config console log report syz C ci-upstream-gce-leak
2020/03/11 04:02 upstream e94148454103 35f53e45 .config console log report syz C ci-upstream-gce-leak
2020/03/10 10:34 upstream 30bb5572ce7a 35f53e45 .config console log report syz C ci-upstream-gce-leak
2020/03/09 13:51 upstream 2c523b344dfa 2e9971bb .config console log report syz C ci-upstream-gce-leak
2020/03/01 17:02 upstream 63623fd44972 c88c7b75 .config console log report syz C ci-upstream-gce-leak
2020/02/25 10:20 upstream f8788d86ab28 59b57593 .config console log report syz C ci-upstream-gce-leak
2020/02/24 10:41 upstream d2eee25858f2 d801cb02 .config console log report syz C ci-upstream-gce-leak
2020/02/23 01:17 upstream 54dedb5b571d 2c36e7a7 .config console log report syz C ci-upstream-gce-leak
2020/02/21 03:40 upstream ca7e1fd1026c bd2a74a3 .config console log report syz C ci-upstream-gce-leak
2020/02/18 20:10 upstream b1da3acc781c 012fbc32 .config console log report syz C ci-upstream-gce-leak
2020/02/18 01:42 upstream 11a48a5a18c6 1ce142dc .config console log report syz C ci-upstream-gce-leak
2020/02/17 23:23 upstream 11a48a5a18c6 2b411596 .config console log report syz C ci-upstream-gce-leak
2020/02/16 03:20 upstream 829e69446995 5d7b90f1 .config console log report syz C ci-upstream-gce-leak
2020/02/15 10:06 upstream 2019fc96af22 5d7b90f1 .config console log report syz C ci-upstream-gce-leak
2020/02/15 09:39 upstream 2019fc96af22 5d7b90f1 .config console log report syz C ci-upstream-gce-leak
2020/02/15 09:10 upstream 2019fc96af22 5d7b90f1 .config console log report syz C ci-upstream-gce-leak
2020/02/13 22:51 upstream 0bf999f9c5e7 c5ed587f .config console log report syz C ci-upstream-gce-leak
2020/02/13 02:05 upstream f2850dd5ee01 84f4fc8a .config console log report syz C ci-upstream-gce-leak
* Struck through repros no longer work on HEAD.