From: syzbot <syzbot+7f10c1653e35933c0f1e@syzkaller.appspotmail.com>
To: arve@android.com, brauner@kernel.org, cmllamas@google.com,
gregkh@linuxfoundation.org, joel@joelfernandes.org,
linux-kernel@vger.kernel.org, maco@android.com,
surenb@google.com, syzkaller-bugs@googlegroups.com,
tkjos@android.com
Subject: [syzbot] memory leak in binder_transaction (2)
Date: Sun, 20 Nov 2022 13:51:41 -0800 [thread overview]
Message-ID: <000000000000aa181605ededf1fa@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 59d0d52c30d4 AMerge tag 'netfs-fixes-20221115' of git://gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14a7b445880000
kernel config: https://syzkaller.appspot.com/x/.config?x=435fb8cdd395f932
dashboard link: https://syzkaller.appspot.com/bug?extid=7f10c1653e35933c0f1e
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=114a3b35880000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/854c98a663e0/disk-59d0d52c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/233c8e05ab54/vmlinux-59d0d52c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7254f9286f1d/bzImage-59d0d52c.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7f10c1653e35933c0f1e@syzkaller.appspotmail.com
BUG: memory leak
unreferenced object 0xffff88811b0bbe00 (size 32):
comm "syz-executor.1", pid 4041, jiffies 4294986632 (age 15.340s)
hex dump (first 32 bytes):
00 be 0b 1b 81 88 ff ff 00 be 0b 1b 81 88 ff ff ................
03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<ffffffff814ed530>] kmalloc_trace+0x20/0x90 mm/slab_common.c:1045
[<ffffffff8396b973>] kmalloc include/linux/slab.h:553 [inline]
[<ffffffff8396b973>] kzalloc include/linux/slab.h:689 [inline]
[<ffffffff8396b973>] binder_transaction+0xc53/0x3f20 drivers/android/binder.c:3128
[<ffffffff8396f213>] binder_thread_write+0x5d3/0x1790 drivers/android/binder.c:3975
[<ffffffff839726cb>] binder_ioctl_write_read drivers/android/binder.c:5034 [inline]
[<ffffffff839726cb>] binder_ioctl+0x22fb/0x3a30 drivers/android/binder.c:5321
[<ffffffff8161f20c>] vfs_ioctl fs/ioctl.c:51 [inline]
[<ffffffff8161f20c>] __do_sys_ioctl fs/ioctl.c:870 [inline]
[<ffffffff8161f20c>] __se_sys_ioctl fs/ioctl.c:856 [inline]
[<ffffffff8161f20c>] __x64_sys_ioctl+0xfc/0x140 fs/ioctl.c:856
[<ffffffff848802d5>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
[<ffffffff848802d5>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
[<ffffffff84a00087>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
---
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:[~2022-11-20 21:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 21:51 syzbot [this message]
2023-09-11 20:56 ` [syzbot] [kernel?] memory leak in binder_transaction (2) syzbot
2023-09-22 4:42 ` [PATCH] binder: fix memory leak of spamming work Carlos Llamas
2023-09-22 17:51 ` [PATCH v2] binder: fix memory leaks of spam and pending work Carlos Llamas
2023-09-22 18:50 ` Alice Ryhl
2023-09-25 18:46 ` Todd Kjos
[not found] <20221121015757.4942-1-hdanton@sina.com>
2022-11-21 2:32 ` [syzbot] memory leak in binder_transaction (2) 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=000000000000aa181605ededf1fa@google.com \
--to=syzbot+7f10c1653e35933c0f1e@syzkaller.appspotmail.com \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=cmllamas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=surenb@google.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tkjos@android.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.