From: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: herbert@gondor.apana.org.au, cohuck@redhat.com,
nhorman@redhat.com, vdronov@redhat.com, bhelgaas@google.com,
mark.a.chambers@intel.com, gordon.mcfadden@intel.com,
ahsan.atta@intel.com, fiona.trahe@intel.com, qat-linux@intel.com,
kvm@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/5] vfio/pci: Add device denylist
Date: Fri, 24 Jul 2020 09:34:17 +0100 [thread overview]
Message-ID: <20200724083417.GA3913@silpixa00400314> (raw)
In-Reply-To: <20200723164126.0249b247@w520.home>
On Thu, Jul 23, 2020 at 04:41:26PM -0600, Alex Williamson wrote:
> On Thu, 23 Jul 2020 22:47:02 +0100
> Giovanni Cabiddu <giovanni.cabiddu@intel.com> wrote:
>
> > Add denylist of devices that by default are not probed by vfio-pci.
> > Devices in this list may be susceptible to untrusted application, even
> > if the IOMMU is enabled. To be accessed via vfio-pci, the user has to
> > explicitly disable the denylist.
> >
> > The denylist can be disabled via the module parameter disable_denylist.
> >
> > Signed-off-by: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
> > ---
> > drivers/vfio/pci/vfio_pci.c | 33 +++++++++++++++++++++++++++++++++
> > 1 file changed, 33 insertions(+)
> >
> > diff --git a/drivers/vfio/pci/vfio_pci.c b/drivers/vfio/pci/vfio_pci.c
> > index 7c0779018b1b..673f53c4798e 100644
> > --- a/drivers/vfio/pci/vfio_pci.c
> > +++ b/drivers/vfio/pci/vfio_pci.c
> > @@ -60,6 +60,10 @@ module_param(enable_sriov, bool, 0644);
> > MODULE_PARM_DESC(enable_sriov, "Enable support for SR-IOV configuration. Enabling SR-IOV on a PF typically requires support of the userspace PF driver, enabling VFs without such support may result in non-functional VFs or PF.");
> > #endif
> >
> > +static bool disable_denylist;
> > +module_param(disable_denylist, bool, 0444);
> > +MODULE_PARM_DESC(disable_denylist, "Disable use of device denylist. Disabling the denylist prevents binding to devices with known errata that may lead to exploitable stability or security issues when accessed by untrusted users.");
>
> s/prevents/allows/
>
> ie. the denylist prevents binding, therefore disabling the denylist
> allows binding
>
> I can fix this on commit without a new version if you agree. I also
> see that patch 1/5 didn't change since v2, so I'll transfer Bjorn's
> ack. If that sounds good I'll queue the first 3 patches in my next
> branch for v5.9. Thanks,
My bad, apologies! I'm ok also to re-spin adding Bjorn's ack and the fix
above.
Regards,
--
Giovanni
next prev parent reply other threads:[~2020-07-24 8:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 21:47 [PATCH v3 0/5] vfio/pci: add denylist and disable qat Giovanni Cabiddu
2020-07-23 21:47 ` [PATCH v3 1/5] PCI: Add Intel QuickAssist device IDs Giovanni Cabiddu
2020-07-23 21:47 ` [PATCH v3 2/5] vfio/pci: Add device denylist Giovanni Cabiddu
2020-07-23 22:41 ` Alex Williamson
2020-07-24 8:34 ` Giovanni Cabiddu [this message]
2020-07-23 21:47 ` [PATCH v3 3/5] vfio/pci: Add QAT devices to denylist Giovanni Cabiddu
2020-07-23 21:47 ` [PATCH v3 4/5] crypto: qat - replace device ids defines Giovanni Cabiddu
2020-07-23 21:47 ` [PATCH v3 5/5] crypto: qat - use PCI_VDEVICE Giovanni Cabiddu
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=20200724083417.GA3913@silpixa00400314 \
--to=giovanni.cabiddu@intel.com \
--cc=ahsan.atta@intel.com \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=cohuck@redhat.com \
--cc=fiona.trahe@intel.com \
--cc=gordon.mcfadden@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=kvm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mark.a.chambers@intel.com \
--cc=nhorman@redhat.com \
--cc=qat-linux@intel.com \
--cc=vdronov@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