Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH net] vsock/loopback: use only sk_buff_head.lock to protect the
 packet queue
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <167990161811.4487.17278563612725612411.git-patchwork-notify@kernel.org>
Date:   Mon, 27 Mar 2023 07:20:18 +0000
References: <20230324115450.11268-1-sgarzare@redhat.com>
In-Reply-To: <20230324115450.11268-1-sgarzare@redhat.com>
To:     Stefano Garzarella <sgarzare@redhat.com>
Cc:     netdev@vger.kernel.org, bobby.eshleman@bytedance.com,
        davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
        linux-kernel@vger.kernel.org, avkrasnov@sberdevices.ru,
        kuba@kernel.org, virtualization@lists.linux-foundation.org,
        syzbot+befff0a9536049e7902e@syzkaller.appspotmail.com
Precedence: bulk

Hello:

This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:

On Fri, 24 Mar 2023 12:54:50 +0100 you wrote:
> pkt_list_lock was used before commit 71dc9ec9ac7d ("virtio/vsock:
> replace virtio_vsock_pkt with sk_buff") to protect the packet queue.
> After that commit we switched to sk_buff and we are using
> sk_buff_head.lock in almost every place to protect the packet queue
> except in vsock_loopback_work() when we call skb_queue_splice_init().
> 
> As reported by syzbot, this caused unlocked concurrent access to the
> packet queue between vsock_loopback_work() and
> vsock_loopback_cancel_pkt() since it is not holding pkt_list_lock.
> 
> [...]

Here is the summary with links:
  - [net] vsock/loopback: use only sk_buff_head.lock to protect the packet queue
    https://git.kernel.org/netdev/net/c/b465518dc27d

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