From: syzbot <syzbot+305326672fed51b205f7@syzkaller.appspotmail.com>
To: davem@davemloft.net, dhowells@redhat.com,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: memory leak in rxrpc_lookup_local
Date: Tue, 22 Oct 2019 15:44:12 -0700 [thread overview]
Message-ID: <000000000000065d240595878a92@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 4fe34d61 Merge branch 'x86-urgent-for-linus' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11b21d40e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=cd7f8e43c7bdf83a
dashboard link: https://syzkaller.appspot.com/bug?extid=305326672fed51b205f7
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e692ff600000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10af816b600000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+305326672fed51b205f7@syzkaller.appspotmail.com
BUG: memory leak
unreferenced object 0xffff888121f35e00 (size 256):
comm "syz-executor362", pid 6892, jiffies 4294941791 (age 7.710s)
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 09 00 00 00 00 80 e7 21 81 88 ff ff ...........!....
backtrace:
[<000000006221752a>] kmemleak_alloc_recursive
include/linux/kmemleak.h:43 [inline]
[<000000006221752a>] slab_post_alloc_hook mm/slab.h:586 [inline]
[<000000006221752a>] slab_alloc mm/slab.c:3319 [inline]
[<000000006221752a>] kmem_cache_alloc_trace+0x145/0x2c0 mm/slab.c:3548
[<000000006ee28c35>] kmalloc include/linux/slab.h:556 [inline]
[<000000006ee28c35>] kzalloc include/linux/slab.h:690 [inline]
[<000000006ee28c35>] rxrpc_alloc_local net/rxrpc/local_object.c:79
[inline]
[<000000006ee28c35>] rxrpc_lookup_local+0x1aa/0x750
net/rxrpc/local_object.c:277
[<000000009255b1c3>] rxrpc_bind+0x131/0x1e0 net/rxrpc/af_rxrpc.c:149
[<00000000d7bcf378>] __sys_bind+0x11c/0x140 net/socket.c:1647
[<00000000c269c3cb>] __do_sys_bind net/socket.c:1658 [inline]
[<00000000c269c3cb>] __se_sys_bind net/socket.c:1656 [inline]
[<00000000c269c3cb>] __x64_sys_bind+0x1e/0x30 net/socket.c:1656
[<000000000444b7d1>] do_syscall_64+0x73/0x1f0
arch/x86/entry/common.c:290
[<000000001700d564>] 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
reply other threads:[~2019-10-22 22:44 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=000000000000065d240595878a92@google.com \
--to=syzbot+305326672fed51b205f7@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@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 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.