Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v2 1/1] vsock: fix the race conditions in multi-transport
 support
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <161223840744.29348.6975246146992657399.git-patchwork-notify@kernel.org>
Date:   Tue, 02 Feb 2021 04:00:07 +0000
References: <20210201084719.2257066-1-alex.popov@linux.com>
In-Reply-To: <20210201084719.2257066-1-alex.popov@linux.com>
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
Precedence: bulk

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