From: syzbot <syzbot+128f4dd6e796c98b3760@syzkaller.appspotmail.com>
To: jack@suse.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: memory leak in udf_process_sequence
Date: Mon, 21 Sep 2020 03:02:21 -0700 [thread overview]
Message-ID: <0000000000004c1f4d05afcff2f4@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 325d0eab Merge branch 'akpm' (patches from Andrew)
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13ec44d3900000
kernel config: https://syzkaller.appspot.com/x/.config?x=a1f3c5052e8097e9
dashboard link: https://syzkaller.appspot.com/bug?extid=128f4dd6e796c98b3760
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=101a0e9b900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17ae18d3900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+128f4dd6e796c98b3760@syzkaller.appspotmail.com
BUG: memory leak
unreferenced object 0xffff88811a1d0a00 (size 512):
comm "syz-executor299", pid 6519, jiffies 4294943224 (age 15.090s)
hex dump (first 32 bytes):
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 00 ................
backtrace:
[<000000009ea2686e>] kmalloc include/linux/slab.h:554 [inline]
[<000000009ea2686e>] kmalloc_array include/linux/slab.h:593 [inline]
[<000000009ea2686e>] kcalloc include/linux/slab.h:605 [inline]
[<000000009ea2686e>] udf_process_sequence+0x7e/0x1080 fs/udf/super.c:1676
[<00000000d9f60715>] udf_load_sequence fs/udf/super.c:1795 [inline]
[<00000000d9f60715>] udf_check_anchor_block+0xdc/0x1a0 fs/udf/super.c:1835
[<0000000067395456>] udf_scan_anchors+0x9e/0x240 fs/udf/super.c:1868
[<00000000966a1b37>] udf_find_anchor fs/udf/super.c:1925 [inline]
[<00000000966a1b37>] udf_load_vrs+0x1be/0x3b0 fs/udf/super.c:1990
[<0000000004bba192>] udf_fill_super+0x286/0x7a5 fs/udf/super.c:2183
[<00000000d48efb9b>] mount_bdev+0x1d3/0x210 fs/super.c:1417
[<00000000280e173c>] legacy_get_tree+0x26/0x70 fs/fs_context.c:592
[<0000000059fde270>] vfs_get_tree+0x28/0xe0 fs/super.c:1547
[<00000000904c79e7>] do_new_mount fs/namespace.c:2875 [inline]
[<00000000904c79e7>] path_mount+0x90e/0xda0 fs/namespace.c:3192
[<000000008e0f8bcd>] do_mount fs/namespace.c:3205 [inline]
[<000000008e0f8bcd>] __do_sys_mount fs/namespace.c:3413 [inline]
[<000000008e0f8bcd>] __se_sys_mount fs/namespace.c:3390 [inline]
[<000000008e0f8bcd>] __x64_sys_mount+0x140/0x190 fs/namespace.c:3390
[<00000000e981acac>] do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
[<000000006322386a>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2020-09-21 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 10:02 syzbot [this message]
2020-09-22 15:45 ` [Linux-kernel-mentees] [PATCH] udf: Fix memory leak in udf_process_sequence() Peilin Ye
2020-09-23 10:04 ` Jan Kara
2020-09-23 10:29 ` Peilin Ye
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0000000000004c1f4d05afcff2f4@google.com \
--to=syzbot+128f4dd6e796c98b3760@syzkaller.appspotmail.com \
--cc=jack@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox