From: patchwork-bot+netdevbpf@kernel.org
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: kuba@kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, davem@davemloft.net,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
asias@redhat.com, mst@redhat.com, imbrenda@linux.vnet.ibm.com,
stefanha@redhat.com
Subject: Re: [PATCH net] vsock/virtio: update credit only if socket is not closed
Date: Mon, 08 Feb 2021 21:40:07 +0000 [thread overview]
Message-ID: <161282040728.13562.4928332686519436611.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210208144454.84438-1-sgarzare@redhat.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Mon, 8 Feb 2021 15:44:54 +0100 you wrote:
> If the socket is closed or is being released, some resources used by
> virtio_transport_space_update() such as 'vsk->trans' may be released.
>
> To avoid a use after free bug we should only update the available credit
> when we are sure the socket is still open and we have the lock held.
>
> Fixes: 06a8fc78367d ("VSOCK: Introduce virtio_vsock_common.ko")
> Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
>
> [...]
Here is the summary with links:
- [net] vsock/virtio: update credit only if socket is not closed
https://git.kernel.org/netdev/net/c/ce7536bc7398
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-08 21:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 14:44 [PATCH net] vsock/virtio: update credit only if socket is not closed Stefano Garzarella
2021-02-08 14:44 ` Stefano Garzarella
2021-02-08 18:32 ` Michael S. Tsirkin
2021-02-08 18:32 ` Michael S. Tsirkin
2021-02-08 21:40 ` 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=161282040728.13562.4928332686519436611.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=asias@redhat.com \
--cc=davem@davemloft.net \
--cc=imbrenda@linux.vnet.ibm.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.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 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.