From: patchwork-bot+netdevbpf@kernel.org
To: Ziyang Xuan <william.xuanziyang@huawei.com>
Cc: mani@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
linux-arm-msm@vger.kernel.org, netdev@vger.kernel.org,
andersson@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: qrtr: Fix a refcount bug in qrtr_recvmsg()
Date: Fri, 31 Mar 2023 08:20:17 +0000 [thread overview]
Message-ID: <168025081712.23963.16327516163139075912.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230330012532.1065159-1-william.xuanziyang@huawei.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 30 Mar 2023 09:25:32 +0800 you wrote:
> Syzbot reported a bug as following:
>
> refcount_t: addition on 0; use-after-free.
> ...
> RIP: 0010:refcount_warn_saturate+0x17c/0x1f0 lib/refcount.c:25
> ...
> Call Trace:
> <TASK>
> __refcount_add include/linux/refcount.h:199 [inline]
> __refcount_inc include/linux/refcount.h:250 [inline]
> refcount_inc include/linux/refcount.h:267 [inline]
> kref_get include/linux/kref.h:45 [inline]
> qrtr_node_acquire net/qrtr/af_qrtr.c:202 [inline]
> qrtr_node_lookup net/qrtr/af_qrtr.c:398 [inline]
> qrtr_send_resume_tx net/qrtr/af_qrtr.c:1003 [inline]
> qrtr_recvmsg+0x85f/0x990 net/qrtr/af_qrtr.c:1070
> sock_recvmsg_nosec net/socket.c:1017 [inline]
> sock_recvmsg+0xe2/0x160 net/socket.c:1038
> qrtr_ns_worker+0x170/0x1700 net/qrtr/ns.c:688
> process_one_work+0x991/0x15c0 kernel/workqueue.c:2390
> worker_thread+0x669/0x1090 kernel/workqueue.c:2537
>
> [...]
Here is the summary with links:
- [net] net: qrtr: Fix a refcount bug in qrtr_recvmsg()
https://git.kernel.org/netdev/net/c/44d807320000
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:[~2023-03-31 8:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 1:25 [PATCH net] net: qrtr: Fix a refcount bug in qrtr_recvmsg() Ziyang Xuan
2023-03-31 8:20 ` 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=168025081712.23963.16327516163139075912.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andersson@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=william.xuanziyang@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