syzbot


memory leak in path_openat (2)

Status: upstream: reported C repro on 2021/02/17 05:21
Subsystems: fs
[Documentation on labels]
Reported-by: syzbot+921ef0ccfeed3a496721@syzkaller.appspotmail.com
First crash: 1156d, last: 126d
Discussions (1)
Title Replies (including bot) Last reply
memory leak in path_openat (2) 1 (2) 2021/02/17 05:41
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream memory leak in path_openat fs C 1 1568d 1564d 0/26 closed as invalid on 2020/03/07 22:28
Last patch testing requests (10)
Created Duration User Patch Repo Result
2024/04/14 14:41 14m retest repro upstream report log
2024/04/14 14:41 13m retest repro upstream error OK
2024/03/24 12:03 12m retest repro upstream report log
2024/03/04 03:23 19m retest repro upstream log
2024/01/30 16:05 13m retest repro upstream report log
2024/01/30 16:05 17m retest repro upstream error OK
2024/01/13 10:00 16m retest repro upstream report log
2023/12/24 15:07 15m retest repro upstream report log
2023/11/18 00:21 15m retest repro upstream report log
2023/11/18 00:21 11m retest repro upstream error OK

Sample crash report:
write to /proc/sys/kernel/softlockup_all_cpu_backtrace failed: No such file or directory
BUG: memory leak
unreferenced object 0xffff88810e25c500 (size 256):
  comm "syz-executor301", pid 3624, jiffies 4294943948 (age 13.360s)
  hex dump (first 32 bytes):
    10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    e0 91 ba 41 81 88 ff ff 80 71 ef 0e 81 88 ff ff  ...A.....q......
  backtrace:
    [<ffffffff815fbc0f>] kmem_cache_zalloc include/linux/slab.h:679 [inline]
    [<ffffffff815fbc0f>] __alloc_file+0x1f/0xf0 fs/file_table.c:138
    [<ffffffff815fc359>] alloc_empty_file+0x69/0x120 fs/file_table.c:187
    [<ffffffff8161512e>] path_openat+0x4e/0x1b70 fs/namei.c:3700
    [<ffffffff816194f1>] do_filp_open+0xc1/0x1b0 fs/namei.c:3741
    [<ffffffff815f3add>] do_sys_openat2+0xed/0x260 fs/open.c:1310
    [<ffffffff815f452f>] do_sys_open fs/open.c:1326 [inline]
    [<ffffffff815f452f>] __do_sys_openat fs/open.c:1342 [inline]
    [<ffffffff815f452f>] __se_sys_openat fs/open.c:1337 [inline]
    [<ffffffff815f452f>] __x64_sys_openat+0x7f/0xe0 fs/open.c:1337
    [<ffffffff8485b3b5>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
    [<ffffffff8485b3b5>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
    [<ffffffff84a00087>] entry_SYSCALL_64_after_hwframe+0x63/0xcd

write to /proc/sys/kernel/hung_task_check_interval_secs failed: No such file or directory
write to /proc/sys/kernel/softlockup_all_cpu_backtrace failed: No such file or directory

Crashes (5):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/12/03 17:13 upstream a4412fdd49dc e080de16 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-leak memory leak in path_openat
2021/02/13 05:13 upstream dcc0b49040c7 98682e5e .config console log report syz C ci-upstream-gce-leak memory leak in path_openat
2023/12/10 14:28 upstream c527f5606aa5 28b24332 .config console log report syz [disk image] [vmlinux] [kernel image] ci-upstream-gce-leak memory leak in path_openat
2023/07/12 06:27 upstream 3f01e9fed845 2f19aa4f .config console log report syz [disk image] [vmlinux] [kernel image] ci-upstream-gce-leak memory leak in path_openat
2021/09/11 01:03 upstream bf9f243f23e6 5ae8508a .config console log report syz ci-upstream-gce-leak memory leak in path_openat
* Struck through repros no longer work on HEAD.