[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <164562001051.25344.13267452544338970366.git-patchwork-notify@kernel.org>
Date: Wed, 23 Feb 2022 12:40:10 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Stefano Garzarella <sgarzare@...hat.com>
Cc: mst@...hat.com, stefanha@...hat.com, jasowang@...hat.com,
netdev@...r.kernel.org, virtualization@...ts.linux-foundation.org,
syzbot+1e3ea63db39f2b4440e0@...kaller.appspotmail.com,
kvm@...r.kernel.org, mail@...rudhrb.com,
syzbot+3140b17cb44a7b174008@...kaller.appspotmail.com,
linux-kernel@...r.kernel.org, michael.christie@...cle.com,
dan.carpenter@...cle.com, stable@...r.kernel.org
Subject: Re: [PATCH v2] vhost/vsock: don't check owner in vhost_vsock_stop() while
releasing
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@...emloft.net>:
On Tue, 22 Feb 2022 10:47:42 +0100 you wrote:
> vhost_vsock_stop() calls vhost_dev_check_owner() to check the device
> ownership. It expects current->mm to be valid.
>
> vhost_vsock_stop() is also called by vhost_vsock_dev_release() when
> the user has not done close(), so when we are in do_exit(). In this
> case current->mm is invalid and we're releasing the device, so we
> should clean it anyway.
>
> [...]
Here is the summary with links:
- [v2] vhost/vsock: don't check owner in vhost_vsock_stop() while releasing
https://git.kernel.org/netdev/net/c/a58da53ffd70
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists