From: syzbot <syzbot+f317896aae32eb281a58@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
miquel.raynal@bootlin.com, richard@nod.at,
syzkaller-bugs@googlegroups.com, vigneshr@ti.com
Subject: memory leak in erase_aeb
Date: Sun, 08 Dec 2019 11:35:08 -0800 [thread overview]
Message-ID: <0000000000006d0a820599366088@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: ad910e36 pipe: fix poll/select race introduced by the pipe..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16080232e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=3beca47aecbf4a9c
dashboard link: https://syzkaller.appspot.com/bug?extid=f317896aae32eb281a58
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14b527f2e00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+f317896aae32eb281a58@syzkaller.appspotmail.com
BUG: memory leak
unreferenced object 0xffff8881225039a0 (size 32):
comm "syz-executor.0", pid 7318, jiffies 4294950453 (age 8.280s)
hex dump (first 32 bytes):
00 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 01 00 00 00 02 00 00 00 ................
backtrace:
[<000000003a9d0e7e>] kmemleak_alloc_recursive
include/linux/kmemleak.h:43 [inline]
[<000000003a9d0e7e>] slab_post_alloc_hook mm/slab.h:586 [inline]
[<000000003a9d0e7e>] slab_alloc mm/slab.c:3320 [inline]
[<000000003a9d0e7e>] kmem_cache_alloc+0x13f/0x2c0 mm/slab.c:3484
[<00000000b53dfd0a>] erase_aeb+0x2a/0x100 drivers/mtd/ubi/wl.c:1691
[<000000005ccfba82>] ubi_wl_init+0x1ae/0x600 drivers/mtd/ubi/wl.c:1758
[<000000002350928f>] ubi_attach+0x665/0x18e7
drivers/mtd/ubi/attach.c:1605
[<0000000055aac88b>] ubi_attach_mtd_dev+0x5b3/0xd40
drivers/mtd/ubi/build.c:946
[<00000000071dc178>] ctrl_cdev_ioctl+0x149/0x1c0
drivers/mtd/ubi/cdev.c:1043
[<000000004c359338>] vfs_ioctl fs/ioctl.c:47 [inline]
[<000000004c359338>] file_ioctl fs/ioctl.c:545 [inline]
[<000000004c359338>] do_vfs_ioctl+0x551/0x890 fs/ioctl.c:732
[<000000002f3b4a0e>] ksys_ioctl+0x86/0xb0 fs/ioctl.c:749
[<0000000071dee951>] __do_sys_ioctl fs/ioctl.c:756 [inline]
[<0000000071dee951>] __se_sys_ioctl fs/ioctl.c:754 [inline]
[<0000000071dee951>] __x64_sys_ioctl+0x1e/0x30 fs/ioctl.c:754
[<0000000069d4ede5>] do_syscall_64+0x73/0x220
arch/x86/entry/common.c:294
[<000000001a44675f>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+f317896aae32eb281a58@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
miquel.raynal@bootlin.com, richard@nod.at,
syzkaller-bugs@googlegroups.com, vigneshr@ti.com
Subject: memory leak in erase_aeb
Date: Sun, 08 Dec 2019 11:35:08 -0800 [thread overview]
Message-ID: <0000000000006d0a820599366088@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: ad910e36 pipe: fix poll/select race introduced by the pipe..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16080232e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=3beca47aecbf4a9c
dashboard link: https://syzkaller.appspot.com/bug?extid=f317896aae32eb281a58
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14b527f2e00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+f317896aae32eb281a58@syzkaller.appspotmail.com
BUG: memory leak
unreferenced object 0xffff8881225039a0 (size 32):
comm "syz-executor.0", pid 7318, jiffies 4294950453 (age 8.280s)
hex dump (first 32 bytes):
00 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 01 00 00 00 02 00 00 00 ................
backtrace:
[<000000003a9d0e7e>] kmemleak_alloc_recursive
include/linux/kmemleak.h:43 [inline]
[<000000003a9d0e7e>] slab_post_alloc_hook mm/slab.h:586 [inline]
[<000000003a9d0e7e>] slab_alloc mm/slab.c:3320 [inline]
[<000000003a9d0e7e>] kmem_cache_alloc+0x13f/0x2c0 mm/slab.c:3484
[<00000000b53dfd0a>] erase_aeb+0x2a/0x100 drivers/mtd/ubi/wl.c:1691
[<000000005ccfba82>] ubi_wl_init+0x1ae/0x600 drivers/mtd/ubi/wl.c:1758
[<000000002350928f>] ubi_attach+0x665/0x18e7
drivers/mtd/ubi/attach.c:1605
[<0000000055aac88b>] ubi_attach_mtd_dev+0x5b3/0xd40
drivers/mtd/ubi/build.c:946
[<00000000071dc178>] ctrl_cdev_ioctl+0x149/0x1c0
drivers/mtd/ubi/cdev.c:1043
[<000000004c359338>] vfs_ioctl fs/ioctl.c:47 [inline]
[<000000004c359338>] file_ioctl fs/ioctl.c:545 [inline]
[<000000004c359338>] do_vfs_ioctl+0x551/0x890 fs/ioctl.c:732
[<000000002f3b4a0e>] ksys_ioctl+0x86/0xb0 fs/ioctl.c:749
[<0000000071dee951>] __do_sys_ioctl fs/ioctl.c:756 [inline]
[<0000000071dee951>] __se_sys_ioctl fs/ioctl.c:754 [inline]
[<0000000071dee951>] __x64_sys_ioctl+0x1e/0x30 fs/ioctl.c:754
[<0000000069d4ede5>] do_syscall_64+0x73/0x220
arch/x86/entry/common.c:294
[<000000001a44675f>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2019-12-08 19:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-08 19:35 syzbot [this message]
2019-12-08 19:35 ` memory leak in erase_aeb syzbot
2019-12-20 2:14 ` [PATCH] UBI: Fastmap: free unused fastmap anchor peb during detach Hou Tao
2020-01-06 9:02 ` Sascha Hauer
2020-01-12 22:51 ` Richard Weinberger
2020-01-11 17:19 ` memory leak in erase_aeb syzbot
2020-01-11 17:19 ` syzbot
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=0000000000006d0a820599366088@google.com \
--to=syzbot+f317896aae32eb281a58@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.