From: syzbot <syzbot+0bac5fec63d4f399ba98@syzkaller.appspotmail.com>
To: axboe@kernel.dk, christian@brauner.io, ebiederm@xmission.com,
elver@google.com, linux-kernel@vger.kernel.org, oleg@redhat.com,
pcc@google.com, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de
Subject: [syzbot] memory leak in __send_signal
Date: Sun, 06 Jun 2021 07:32:23 -0700 [thread overview]
Message-ID: <000000000000148b4b05c419cbbb@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 9d32fa5d Merge tag 'net-5.13-rc5' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10fd97dfd00000
kernel config: https://syzkaller.appspot.com/x/.config?x=de8efb0998945e75
dashboard link: https://syzkaller.appspot.com/bug?extid=0bac5fec63d4f399ba98
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16029ce0300000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+0bac5fec63d4f399ba98@syzkaller.appspotmail.com
2021/06/05 21:42:36 executed programs: 303
2021/06/05 21:42:42 executed programs: 312
2021/06/05 21:42:48 executed programs: 319
2021/06/05 21:42:54 executed programs: 331
BUG: memory leak
unreferenced object 0xffff8881278e3c80 (size 80):
comm "syz-executor.4", pid 12851, jiffies 4295068441 (age 14.610s)
hex dump (first 32 bytes):
80 3c 8e 27 81 88 ff ff 80 3c 8e 27 81 88 ff ff .<.'.....<.'....
00 00 00 00 00 00 00 00 05 00 00 00 00 00 00 00 ................
backtrace:
[<ffffffff812450d6>] __sigqueue_alloc+0xd6/0x240 kernel/signal.c:441
[<ffffffff81247d31>] __send_signal+0x231/0x600 kernel/signal.c:1155
[<ffffffff8124b123>] do_send_sig_info+0x63/0xc0 kernel/signal.c:1333
[<ffffffff8124b4f9>] do_send_specific+0xc9/0xf0 kernel/signal.c:3881
[<ffffffff8124b5ab>] do_tkill+0x8b/0xb0 kernel/signal.c:3907
[<ffffffff8124e811>] __do_sys_tkill kernel/signal.c:3942 [inline]
[<ffffffff8124e811>] __se_sys_tkill kernel/signal.c:3936 [inline]
[<ffffffff8124e811>] __x64_sys_tkill+0x31/0x50 kernel/signal.c:3936
[<ffffffff843540da>] do_syscall_64+0x3a/0xb0 arch/x86/entry/common.c:47
[<ffffffff84400068>] entry_SYSCALL_64_after_hwframe+0x44/0xae
---
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:[~2021-06-06 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 14:32 syzbot [this message]
2021-06-21 23:08 ` [PATCH] signal: Prevent sigqueue caching after task got released Thomas Gleixner
2021-06-22 6:34 ` Oleg Nesterov
2021-06-22 7:59 ` Thomas Gleixner
2021-06-22 8:06 ` Christian Brauner
2021-06-22 13:59 ` [tip: core/urgent] " tip-bot2 for Thomas Gleixner
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=000000000000148b4b05c419cbbb@google.com \
--to=syzbot+0bac5fec63d4f399ba98@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=christian@brauner.io \
--cc=ebiederm@xmission.com \
--cc=elver@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=pcc@google.com \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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).