From: syzbot <syzbot+d9aab50b1154e3d163f5@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 (2)
Date: Mon, 11 May 2020 11:21:20 -0700 [thread overview]
Message-ID: <000000000000e1accc05a563699e@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 2ef96a5b Linux 5.7-rc5
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1383fd32100000
kernel config: https://syzkaller.appspot.com/x/.config?x=c566cc03357343ce
dashboard link: https://syzkaller.appspot.com/bug?extid=d9aab50b1154e3d163f5
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1166ab14100000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+d9aab50b1154e3d163f5@syzkaller.appspotmail.com
BUG: memory leak
unreferenced object 0xffff888127f372c0 (size 32):
comm "syz-executor.0", pid 6931, jiffies 4294945277 (age 14.410s)
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 01 00 00 00 02 00 00 00 ................
backtrace:
[<0000000049aad7d8>] erase_aeb+0x25/0x110 drivers/mtd/ubi/wl.c:1690
[<000000004a6c95d3>] ubi_wl_init+0x193/0x5c0 drivers/mtd/ubi/wl.c:1757
[<00000000a1d58128>] ubi_attach+0x611/0x18ba drivers/mtd/ubi/attach.c:1605
[<00000000eb6b9da4>] ubi_attach_mtd_dev+0x665/0xcc0 drivers/mtd/ubi/build.c:967
[<000000000a8ebd80>] ctrl_cdev_ioctl+0x144/0x1b0 drivers/mtd/ubi/cdev.c:1043
[<000000007ada47ea>] vfs_ioctl fs/ioctl.c:47 [inline]
[<000000007ada47ea>] ksys_ioctl+0xa6/0xd0 fs/ioctl.c:771
[<00000000bd687125>] __do_sys_ioctl fs/ioctl.c:780 [inline]
[<00000000bd687125>] __se_sys_ioctl fs/ioctl.c:778 [inline]
[<00000000bd687125>] __x64_sys_ioctl+0x1a/0x20 fs/ioctl.c:778
[<000000006f0eae66>] do_syscall_64+0x6e/0x220 arch/x86/entry/common.c:295
[<00000000eaee3164>] 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/
reply other threads:[~2020-05-11 18:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=000000000000e1accc05a563699e@google.com \
--to=syzbot+d9aab50b1154e3d163f5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).