From: patchwork-bot+netdevbpf@kernel.org
To: Xin Long <lucien.xin@gmail.com>
Cc: netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, jmaloy@redhat.com, ying.xue@windriver.com
Subject: Re: [PATCH net] tipc: fix a null-ptr-deref in tipc_topsrv_accept
Date: Fri, 21 Oct 2022 05:10:20 +0000 [thread overview]
Message-ID: <166632902051.25874.11226242874677356799.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <4eee264380c409c61c6451af1059b7fb271a7e7b.1666120790.git.lucien.xin@gmail.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 18 Oct 2022 15:19:50 -0400 you wrote:
> syzbot found a crash in tipc_topsrv_accept:
>
> KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]
> Workqueue: tipc_rcv tipc_topsrv_accept
> RIP: 0010:kernel_accept+0x22d/0x350 net/socket.c:3487
> Call Trace:
> <TASK>
> tipc_topsrv_accept+0x197/0x280 net/tipc/topsrv.c:460
> process_one_work+0x991/0x1610 kernel/workqueue.c:2289
> worker_thread+0x665/0x1080 kernel/workqueue.c:2436
> kthread+0x2e4/0x3a0 kernel/kthread.c:376
> ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
>
> [...]
Here is the summary with links:
- [net] tipc: fix a null-ptr-deref in tipc_topsrv_accept
https://git.kernel.org/netdev/net/c/82cb4e4612c6
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-10-21 5:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 19:19 [PATCH net] tipc: fix a null-ptr-deref in tipc_topsrv_accept Xin Long
2022-10-20 14:33 ` Jon Maloy
2022-10-21 5:10 ` 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=166632902051.25874.11226242874677356799.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jmaloy@redhat.com \
--cc=kuba@kernel.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.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 NNTP newsgroup(s).