From: patchwork-bot+netdevbpf@kernel.org
To: shaozhengchao <shaozhengchao@huawei.com>
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
vyasevich@gmail.com, nhorman@tuxdriver.com,
marcelo.leitner@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com, lucien.xin@gmail.com,
weiyongjun1@huawei.com, yuehaibing@huawei.com
Subject: Re: [PATCH net v4] sctp: fix memory leak in sctp_stream_outq_migrate()
Date: Tue, 29 Nov 2022 17:00:18 +0000 [thread overview]
Message-ID: <166974121836.7750.9329219382885985084.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221126031720.378562-1-shaozhengchao@huawei.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 26 Nov 2022 11:17:20 +0800 you wrote:
> When sctp_stream_outq_migrate() is called to release stream out resources,
> the memory pointed to by prio_head in stream out is not released.
>
> The memory leak information is as follows:
> unreferenced object 0xffff88801fe79f80 (size 64):
> comm "sctp_repo", pid 7957, jiffies 4294951704 (age 36.480s)
> hex dump (first 32 bytes):
> 80 9f e7 1f 80 88 ff ff 80 9f e7 1f 80 88 ff ff ................
> 90 9f e7 1f 80 88 ff ff 90 9f e7 1f 80 88 ff ff ................
> backtrace:
> [<ffffffff81b215c6>] kmalloc_trace+0x26/0x60
> [<ffffffff88ae517c>] sctp_sched_prio_set+0x4cc/0x770
> [<ffffffff88ad64f2>] sctp_stream_init_ext+0xd2/0x1b0
> [<ffffffff88aa2604>] sctp_sendmsg_to_asoc+0x1614/0x1a30
> [<ffffffff88ab7ff1>] sctp_sendmsg+0xda1/0x1ef0
> [<ffffffff87f765ed>] inet_sendmsg+0x9d/0xe0
> [<ffffffff8754b5b3>] sock_sendmsg+0xd3/0x120
> [<ffffffff8755446a>] __sys_sendto+0x23a/0x340
> [<ffffffff87554651>] __x64_sys_sendto+0xe1/0x1b0
> [<ffffffff89978b49>] do_syscall_64+0x39/0xb0
> [<ffffffff89a0008b>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
>
> [...]
Here is the summary with links:
- [net,v4] sctp: fix memory leak in sctp_stream_outq_migrate()
https://git.kernel.org/netdev/net/c/9ed7bfc79542
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-11-29 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 3:17 [PATCH net v4] sctp: fix memory leak in sctp_stream_outq_migrate() Zhengchao Shao
2022-11-28 15:36 ` Xin Long
2022-11-29 17:00 ` patchwork-bot+netdevbpf [this message]
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=166974121836.7750.9329219382885985084.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=pabeni@redhat.com \
--cc=shaozhengchao@huawei.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vyasevich@gmail.com \
--cc=weiyongjun1@huawei.com \
--cc=yuehaibing@huawei.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).