From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Eric Biggers <ebiggers@kernel.org>,
linux-fsdevel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [BUG] double fget() in vhost/net (was Re: [PATCH] vfs: move fdput() to right place in ksys_sync_file_range())
Date: Mon, 16 May 2022 03:54:27 -0400 [thread overview]
Message-ID: <20220516035338-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <02ba82ea-727f-1432-226e-ab2eb37d5c29@redhat.com>
On Mon, May 16, 2022 at 12:17:56PM +0800, Jason Wang wrote:
>
> 在 2022/5/15 11:30, Al Viro 写道:
> > [tun/tap and vhost folks Cc'd]
> >
> > here's another piece of code assuming that repeated fget() will yield the
> > same opened file: in vhost_net_set_backend() we have
> >
> > sock = get_socket(fd);
> > if (IS_ERR(sock)) {
> > r = PTR_ERR(sock);
> > goto err_vq;
> > }
> >
> > /* start polling new socket */
> > oldsock = vhost_vq_get_backend(vq);
> > if (sock != oldsock) {
> > ...
> > vhost_vq_set_backend(vq, sock);
> > ...
> > if (index == VHOST_NET_VQ_RX)
> > nvq->rx_ring = get_tap_ptr_ring(fd);
> >
> > with
> > static struct socket *get_socket(int fd)
> > {
> > struct socket *sock;
> >
> > /* special case to disable backend */
> > if (fd == -1)
> > return NULL;
> > sock = get_raw_socket(fd);
> > if (!IS_ERR(sock))
> > return sock;
> > sock = get_tap_socket(fd);
> > if (!IS_ERR(sock))
> > return sock;
> > return ERR_PTR(-ENOTSOCK);
> > }
> > and
> > static struct ptr_ring *get_tap_ptr_ring(int fd)
> > {
> > struct ptr_ring *ring;
> > struct file *file = fget(fd);
> >
> > if (!file)
> > return NULL;
> > ring = tun_get_tx_ring(file);
> > if (!IS_ERR(ring))
> > goto out;
> > ring = tap_get_ptr_ring(file);
> > if (!IS_ERR(ring))
> > goto out;
> > ring = NULL;
> > out:
> > fput(file);
> > return ring;
> > }
> >
> > Again, there is no promise that fd will resolve to the same thing for
> > lookups in get_socket() and in get_tap_ptr_ring(). I'm not familiar
> > enough with the guts of drivers/vhost to tell how easy it is to turn
> > into attack, but it looks like trouble. If nothing else, the pointer
> > returned by tun_get_tx_ring() is not guaranteed to be pinned down by
> > anything - the reference to sock will _usually_ suffice, but that
> > doesn't help any if we get a different socket on that second fget().
> >
> > One possible way to fix it would be the patch below; objections?
> >
> > Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
> > ---
> > diff --git a/drivers/vhost/net.c b/drivers/vhost/net.c
> > index 792ab5f23647..86ea7695241e 100644
> > --- a/drivers/vhost/net.c
> > +++ b/drivers/vhost/net.c
> > @@ -1450,13 +1450,9 @@ static struct socket *get_raw_socket(int fd)
> > return ERR_PTR(r);
> > }
> > -static struct ptr_ring *get_tap_ptr_ring(int fd)
> > +static struct ptr_ring *get_tap_ptr_ring(struct file *file)
> > {
> > struct ptr_ring *ring;
> > - struct file *file = fget(fd);
> > -
> > - if (!file)
> > - return NULL;
> > ring = tun_get_tx_ring(file);
> > if (!IS_ERR(ring))
> > goto out;
> > @@ -1465,7 +1461,6 @@ static struct ptr_ring *get_tap_ptr_ring(int fd)
> > goto out;
> > ring = NULL;
> > out:
> > - fput(file);
> > return ring;
> > }
> > @@ -1553,7 +1548,7 @@ static long vhost_net_set_backend(struct vhost_net *n, unsigned index, int fd)
> > if (r)
> > goto err_used;
> > if (index == VHOST_NET_VQ_RX)
> > - nvq->rx_ring = get_tap_ptr_ring(fd);
> > + nvq->rx_ring = get_tap_ptr_ring(sock->file);
>
>
> sock could be NULL if we want to stop the vhost-net.
Can you cook up a correct patch then please?
> Other looks fine.
>
> Thanks
>
>
> > oldubufs = nvq->ubufs;
> > nvq->ubufs = ubufs;
> >
next prev parent reply other threads:[~2022-05-16 7:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 15:45 [PATCH] vfs: move fdput() to right place in ksys_sync_file_range() Chengguang Xu
2022-05-11 15:51 ` Matthew Wilcox
2022-05-11 19:01 ` Eric Biggers
2022-05-11 21:43 ` Al Viro
2022-05-12 0:28 ` Al Viro
2022-05-12 0:42 ` Jens Axboe
2022-05-12 2:03 ` Alexei Starovoitov
2022-05-12 12:48 ` Brian Vazquez
2022-05-15 3:30 ` [BUG] double fget() in vhost/net (was Re: [PATCH] vfs: move fdput() to right place in ksys_sync_file_range()) Al Viro
2022-05-15 16:14 ` Michael S. Tsirkin
2022-05-16 4:17 ` Jason Wang
2022-05-16 7:54 ` Michael S. Tsirkin [this message]
2022-05-16 8:42 ` Jason Wang
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=20220516035338-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=ebiggers@kernel.org \
--cc=jasowang@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).