From: patchwork-bot+netdevbpf@kernel.org
To: Alexander Popov <alex.popov@linux.com>
Cc: davem@davemloft.net, kuba@kernel.org, sgarzare@redhat.com,
jhansen@vmware.com, stefan@datenfreihafen.org, jeffv@google.com,
greg@kroah.com, torvalds@linuxfoundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] vsock: fix the race conditions in multi-transport support
Date: Tue, 02 Feb 2021 04:00:07 +0000 [thread overview]
Message-ID: <161223840744.29348.6975246146992657399.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210201084719.2257066-1-alex.popov@linux.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Mon, 1 Feb 2021 11:47:19 +0300 you wrote:
> There are multiple similar bugs implicitly introduced by the
> commit c0cfa2d8a788fcf4 ("vsock: add multi-transports support") and
> commit 6a2c0962105ae8ce ("vsock: prevent transport modules unloading").
>
> The bug pattern:
> [1] vsock_sock.transport pointer is copied to a local variable,
> [2] lock_sock() is called,
> [3] the local variable is used.
> VSOCK multi-transport support introduced the race condition:
> vsock_sock.transport value may change between [1] and [2].
>
> [...]
Here is the summary with links:
- [v2,1/1] vsock: fix the race conditions in multi-transport support
https://git.kernel.org/netdev/net/c/c518adafa39f
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:[~2021-02-02 4:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 8:47 [PATCH v2 1/1] vsock: fix the race conditions in multi-transport support Alexander Popov
2021-02-02 4: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=161223840744.29348.6975246146992657399.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alex.popov@linux.com \
--cc=davem@davemloft.net \
--cc=greg@kroah.com \
--cc=jeffv@google.com \
--cc=jhansen@vmware.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sgarzare@redhat.com \
--cc=stefan@datenfreihafen.org \
--cc=torvalds@linuxfoundation.org \
/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