All of lore.kernel.org
 help / color / mirror / Atom feed
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,
	harperchen1110@gmail.com
Subject: Re: [PATCH net 0/2] tipc: fix two race issues in tipc_conn_alloc
Date: Tue, 22 Nov 2022 05:00:21 +0000	[thread overview]
Message-ID: <166909322186.4259.10273863059651319220.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1668807842.git.lucien.xin@gmail.com>

Hello:

This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 18 Nov 2022 16:44:59 -0500 you wrote:
> The race exists beteen tipc_topsrv_accept() and tipc_conn_close(),
> one is allocating the con while the other is freeing it and there
> is no proper lock protecting it. Therefore, a null-pointer-defer
> and a use-after-free may be triggered, see details on each patch.
> 
> Xin Long (2):
>   tipc: set con sock in tipc_conn_alloc
>   tipc: add an extra conn_get in tipc_conn_alloc
> 
> [...]

Here is the summary with links:
  - [net,1/2] tipc: set con sock in tipc_conn_alloc
    https://git.kernel.org/netdev/net/c/0e5d56c64afc
  - [net,2/2] tipc: add an extra conn_get in tipc_conn_alloc
    https://git.kernel.org/netdev/net/c/a7b42969d63f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-11-22  5:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 21:44 [PATCH net 0/2] tipc: fix two race issues in tipc_conn_alloc Xin Long
2022-11-18 21:45 ` [PATCH net 1/2] tipc: set con sock " Xin Long
2022-11-18 21:45 ` [PATCH net 2/2] tipc: add an extra conn_get " Xin Long
2022-11-22  0:47 ` [PATCH net 0/2] tipc: fix two race issues " Jon Maloy
2022-11-22  5: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=166909322186.4259.10273863059651319220.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=harperchen1110@gmail.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 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.