memory leak in journal_init

Status: auto-obsoleted due to no activity on 2024/06/20 18:08
Subsystems: fs
[Documentation on labels]
Reported-by: syzbot+38daa8d09e2bde63614c@syzkaller.appspotmail.com
First crash: 1333d, last: 959d
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [reiserfs?] memory leak in journal_init 0 (1) 2022/12/22 10:27
▶ ▼ Last patch testing requests (10)
Created Duration User Patch Repo Result
2024/06/20 09:29 6h53m retest repro upstream no crash log
2024/06/20 09:29 1h00m retest repro upstream no crash log
2024/04/10 16:38 11h22m retest repro upstream report log
2024/04/10 16:38 11h15m retest repro upstream report log
2024/03/07 09:25 19m retest repro upstream no crash log
2024/02/22 09:21 33m retest repro upstream no crash log
2024/02/08 09:27 29m retest repro upstream no crash log
2024/01/28 04:46 15m retest repro upstream report log
2024/01/28 04:46 14m retest repro upstream report log
2023/12/28 09:10 10m retest repro upstream report log

Sample crash report:
BUG: memory leak
unreferenced object 0xffff88810d223a80 (size 192):
  comm "syz-executor315", pid 5037, jiffies 4294954671 (age 7.890s)
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    01 00 00 00 00 00 00 00 01 00 00 00 03 00 00 00  ................
  backtrace:
    [<ffffffff81574155>] kmalloc_trace+0x25/0x90 mm/slab_common.c:1114
    [<ffffffff81823fc0>] kmalloc include/linux/slab.h:599 [inline]
    [<ffffffff81823fc0>] kzalloc include/linux/slab.h:720 [inline]
    [<ffffffff81823fc0>] alloc_journal_list+0x20/0xb0 fs/reiserfs/journal.c:2573
    [<ffffffff81828227>] journal_list_init fs/reiserfs/journal.c:2587 [inline]
    [<ffffffff81828227>] journal_init+0x7b7/0x1f60 fs/reiserfs/journal.c:2847
    [<ffffffff818139df>] reiserfs_fill_super+0x61f/0x16a0 fs/reiserfs/super.c:2022
    [<ffffffff816925ec>] mount_bdev+0x15c/0x1d0 fs/super.c:1629
    [<ffffffff816f94c9>] legacy_get_tree+0x29/0x80 fs/fs_context.c:638
    [<ffffffff8168f18a>] vfs_get_tree+0x2a/0x130 fs/super.c:1750
    [<ffffffff816d461f>] do_new_mount fs/namespace.c:3335 [inline]
    [<ffffffff816d461f>] path_mount+0xc8f/0x10d0 fs/namespace.c:3662
    [<ffffffff816d5211>] do_mount fs/namespace.c:3675 [inline]
    [<ffffffff816d5211>] __do_sys_mount fs/namespace.c:3884 [inline]
    [<ffffffff816d5211>] __se_sys_mount fs/namespace.c:3861 [inline]
    [<ffffffff816d5211>] __x64_sys_mount+0x1a1/0x1f0 fs/namespace.c:3861
    [<ffffffff84b32fc8>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
    [<ffffffff84b32fc8>] do_syscall_64+0x38/0xb0 arch/x86/entry/common.c:80
    [<ffffffff84c0008b>] entry_SYSCALL_64_after_hwframe+0x63/0xcd

Crashes (5):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/09/24 17:38 upstream 3aba70aed91f 0b6a67ac .config console log report syz C [mounted in repro] ci-upstream-gce-leak memory leak in journal_init
2023/08/21 11:49 upstream f7757129e3de d216d8a0 .config console log report syz C [mounted in repro] ci-upstream-gce-leak memory leak in journal_init
2023/08/01 07:59 upstream 5d0c230f1de8 2a0d0f29 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-leak memory leak in journal_init
2023/04/30 13:15 upstream 825a0714d2b3 62df2017 .config console log report syz C [mounted in repro] ci-upstream-gce-leak memory leak in journal_init
2022/12/18 10:21 upstream f9ff5644bcc0 05494336 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-leak memory leak in journal_init
* Struck through repros no longer work on HEAD.