From: patchwork-bot+netdevbpf@kernel.org
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: mst@redhat.com, stefanha@redhat.com, jasowang@redhat.com,
netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org,
syzbot+1e3ea63db39f2b4440e0@syzkaller.appspotmail.com,
kvm@vger.kernel.org, mail@anirudhrb.com,
syzbot+3140b17cb44a7b174008@syzkaller.appspotmail.com,
linux-kernel@vger.kernel.org, michael.christie@oracle.com,
dan.carpenter@oracle.com, stable@vger.kernel.org
Subject: Re: [PATCH v2] vhost/vsock: don't check owner in vhost_vsock_stop() while releasing
Date: Wed, 23 Feb 2022 12:40:10 +0000 [thread overview]
Message-ID: <164562001051.25344.13267452544338970366.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220222094742.16359-1-sgarzare@redhat.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.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
next prev parent reply other threads:[~2022-02-23 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 9:47 [PATCH v2] vhost/vsock: don't check owner in vhost_vsock_stop() while releasing Stefano Garzarella
2022-02-23 2:09 ` Jason Wang
2022-02-23 12:40 ` patchwork-bot+netdevbpf [this message]
2022-02-24 8:53 ` Stefan Hajnoczi
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=164562001051.25344.13267452544338970366.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@anirudhrb.com \
--cc=michael.christie@oracle.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sgarzare@redhat.com \
--cc=stable@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=syzbot+1e3ea63db39f2b4440e0@syzkaller.appspotmail.com \
--cc=syzbot+3140b17cb44a7b174008@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).