From: Stefan Hajnoczi <stefanha@redhat.com>
To: Greg Kurz <groug@kaod.org>
Cc: mszeredi@redhat.com, Daniel Berrange <berrange@redhat.com>,
slp@redhat.com, qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
virtio-fs@redhat.com, Alex Xu <alex@alxu.ca>,
P J P <ppandit@redhat.com>, Laszlo Ersek <lersek@redhat.com>,
vgoyal@redhat.com
Subject: Re: [PATCH v4 3/3] virtiofsd: prevent opening of special files (CVE-2020-35517)
Date: Wed, 3 Feb 2021 17:06:32 +0000 [thread overview]
Message-ID: <20210203170632.GM74271@stefanha-x1.localdomain> (raw)
In-Reply-To: <20210203165759.352a7f64@bahia.lan>
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
On Wed, Feb 03, 2021 at 04:57:59PM +0100, Greg Kurz wrote:
> On Wed, 3 Feb 2021 11:37:19 +0000
> Stefan Hajnoczi <stefanha@redhat.com> wrote:
> > static int lo_do_open(struct lo_data *lo, struct lo_inode *inode,
> > - struct fuse_file_info *fi)
> > + int existing_fd, struct fuse_file_info *fi)
> > {
> > - char buf[64];
> > ssize_t fh;
> > - int fd;
> > + int fd = existing_fd;
> >
> > update_open_flags(lo->writeback, lo->allow_direct_io, fi);
> >
> > - sprintf(buf, "%i", inode->fd);
> > - fd = openat(lo->proc_self_fd, buf, fi->flags & ~O_NOFOLLOW);
> > - if (fd == -1) {
> > - return -errno;
> > + if (fd < 0) {
> > + fd = lo_inode_open(lo, inode, fi->flags);
> > + if (fd == -1) {
> > + return -errno;
> > + }
>
> lo_inode_open() returns a negative errno already so
> this should be converted to:
>
> if (fd < 0) {
> return fd;
> }
>
> Apart from that LGTM.
Thanks, will fix.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-02-03 17:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 11:37 [PATCH v4 0/3] virtiofsd: prevent opening of special files (CVE-2020-35517) Stefan Hajnoczi
2021-02-03 11:37 ` [PATCH v4 1/3] virtiofsd: extract lo_do_open() from lo_open() Stefan Hajnoczi
2021-02-03 14:20 ` Greg Kurz
2021-02-03 14:47 ` Dr. David Alan Gilbert
2021-02-03 15:45 ` Greg Kurz
2021-02-03 17:47 ` Greg Kurz
2021-02-03 16:57 ` Stefan Hajnoczi
2021-02-03 11:37 ` [PATCH v4 2/3] virtiofsd: optionally return inode pointer from lo_do_lookup() Stefan Hajnoczi
2021-02-03 14:20 ` Greg Kurz
2021-02-03 17:00 ` Stefan Hajnoczi
2021-02-04 8:25 ` Greg Kurz
2021-02-04 9:45 ` Stefan Hajnoczi
2021-02-04 11:19 ` Greg Kurz
2021-02-03 11:37 ` [PATCH v4 3/3] virtiofsd: prevent opening of special files (CVE-2020-35517) Stefan Hajnoczi
2021-02-03 15:28 ` Vivek Goyal
2021-02-03 16:02 ` Greg Kurz
2021-02-03 16:08 ` Vivek Goyal
2021-02-03 17:05 ` Stefan Hajnoczi
2021-02-03 18:05 ` Dr. David Alan Gilbert
2021-02-03 21:14 ` Vivek Goyal
2021-02-04 9:47 ` Stefan Hajnoczi
2021-02-03 15:57 ` Greg Kurz
2021-02-03 17:06 ` Stefan Hajnoczi [this message]
2021-02-03 11:46 ` [PATCH v4 0/3] " no-reply
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=20210203170632.GM74271@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=alex@alxu.ca \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=groug@kaod.org \
--cc=lersek@redhat.com \
--cc=mszeredi@redhat.com \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=slp@redhat.com \
--cc=vgoyal@redhat.com \
--cc=virtio-fs@redhat.com \
/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).