From: syzbot <syzbot+afb980676c836b4a0afa@syzkaller.appspotmail.com>
To: davem@davemloft.net, linux-kernel@vger.kernel.org,
linux-x25@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: memory leak in lapb_register
Date: Tue, 21 May 2019 06:43:06 -0700 [thread overview]
Message-ID: <0000000000005c5d1d0589660769@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: f49aa1de Merge tag 'for-5.2-rc1-tag' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1042cd9ca00000
kernel config: https://syzkaller.appspot.com/x/.config?x=61dd9e15a761691d
dashboard link: https://syzkaller.appspot.com/bug?extid=afb980676c836b4a0afa
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11ea4654a00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=100f6f44a00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+afb980676c836b4a0afa@syzkaller.appspotmail.com
g: Permanently added '10.128.0.195' (ECDSA) to the list of known hosts.
executing program
executing program
BUG: memory leak
unreferenced object 0xffff88810dadc400 (size 256):
comm "softirq", pid 0, jiffies 4294947366 (age 12.720s)
hex dump (first 32 bytes):
00 01 00 00 00 00 ad de 00 02 00 00 00 00 ad de ................
00 20 85 17 81 88 ff ff 00 00 00 00 00 00 00 00 . ..............
backtrace:
[<00000000fe4f5aaf>] kmemleak_alloc_recursive
include/linux/kmemleak.h:55 [inline]
[<00000000fe4f5aaf>] slab_post_alloc_hook mm/slab.h:439 [inline]
[<00000000fe4f5aaf>] slab_alloc mm/slab.c:3326 [inline]
[<00000000fe4f5aaf>] kmem_cache_alloc_trace+0x13d/0x280 mm/slab.c:3553
[<0000000050cea448>] kmalloc include/linux/slab.h:547 [inline]
[<0000000050cea448>] kzalloc include/linux/slab.h:742 [inline]
[<0000000050cea448>] lapb_create_cb net/lapb/lapb_iface.c:121 [inline]
[<0000000050cea448>] lapb_register+0x90/0x1c0 net/lapb/lapb_iface.c:158
[<00000000c0d81e26>] x25_asy_open drivers/net/wan/x25_asy.c:482 [inline]
[<00000000c0d81e26>] x25_asy_open_tty+0x26b/0x2f6
drivers/net/wan/x25_asy.c:572
[<00000000bdec8ae5>] tty_ldisc_open.isra.0+0x40/0x70
drivers/tty/tty_ldisc.c:469
[<000000004f64cfca>] tty_set_ldisc+0x149/0x240
drivers/tty/tty_ldisc.c:596
[<00000000d8b98e91>] tiocsetd drivers/tty/tty_io.c:2332 [inline]
[<00000000d8b98e91>] tty_ioctl+0x366/0xa30 drivers/tty/tty_io.c:2592
[<00000000343f2123>] vfs_ioctl fs/ioctl.c:46 [inline]
[<00000000343f2123>] file_ioctl fs/ioctl.c:509 [inline]
[<00000000343f2123>] do_vfs_ioctl+0x62a/0x810 fs/ioctl.c:696
[<00000000b777b7e5>] ksys_ioctl+0x86/0xb0 fs/ioctl.c:713
[<0000000026d5db65>] __do_sys_ioctl fs/ioctl.c:720 [inline]
[<0000000026d5db65>] __se_sys_ioctl fs/ioctl.c:718 [inline]
[<0000000026d5db65>] __x64_sys_ioctl+0x1e/0x30 fs/ioctl.c:718
[<0000000006a4653e>] do_syscall_64+0x76/0x1a0
arch/x86/entry/common.c:301
[<00000000e706c40e>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
executing program
executing program
---
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-05-21 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 13:43 syzbot [this message]
2019-06-16 15:54 ` [PATCH net] lapb: fixed leak of control-blocks Jeremy Sowden
2019-06-17 3:44 ` David Miller
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=0000000000005c5d1d0589660769@google.com \
--to=syzbot+afb980676c836b4a0afa@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-x25@vger.kernel.org \
--cc=netdev@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).