From: Stephen Hemminger <stephen@networkplumber.org>
To: Chas Williams <3chas3@gmail.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@intel.com>,
stable@dpdk.org, dev@dpdk.org,
Jianfeng Tan <jianfeng.tan@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Shijith Thotton <shijith.thotton@caviumnetworks.com>,
Gregory Etelson <gregory@weka.io>,
Harish Patil <harish.patil@cavium.com>,
George Prekas <george.prekas@epfl.ch>,
Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>,
Rasesh Mody <rasesh.mody@cavium.com>,
Lee Roberts <lee.roberts@hpe.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v2] igb_uio: prevent reset for a list of devices
Date: Tue, 7 Nov 2017 14:13:06 +0100 [thread overview]
Message-ID: <CAOaVG17Q8NpV5qqRYRK=tjT_0AYESBRrT=jwDAuzqCcLJtKjGA@mail.gmail.com> (raw)
In-Reply-To: <CAG2-Gkk1Z3ZE3XpyK_FQVLnQb9qeY3tYnny6n9x2m2E0MkFRyA@mail.gmail.com>
On Nov 7, 2017 20:50, "Chas Williams" <3chas3@gmail.com> wrote:
We still have an issue with this and PCI pass-through. If a guest is
restarted while using PCI pass-through and igb_uio issues a
pci_reset_function(), this causes the host to crash.
On Mon, Nov 6, 2017 at 6:55 PM, Thomas Monjalon <thomas@monjalon.net> wrote:
> 06/11/2017 19:48, Ferruh Yigit:
> > Some devices are having problem on device reset that happens during DPDK
> > application exit [1].
> >
> > Create a static list of devices and exclude them from device reset.
> >
> > [1]
> > http://dpdk.org/ml/archives/dev/2017-November/080927.html
> >
> > Fixes: b58eedfc7dd5 ("igb_uio: issue FLR during open and release of
> device file")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> Applied, thanks
>
> An option may be required to disable this exception
> which may be a security hole.
>
>
Which host. Anything guest can do to crash host is a high severity big in
the host
next prev parent reply other threads:[~2017-11-07 13:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 22:38 [dpdk-dev] [PATCH] " Ferruh Yigit
2017-11-03 23:03 ` Thomas Monjalon
2017-11-04 0:56 ` Mody, Rasesh
2017-11-06 18:48 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2017-11-06 23:55 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2017-11-07 11:50 ` Chas Williams
2017-11-07 13:02 ` Thomas Monjalon
2017-11-07 18:12 ` Chas Williams
2017-11-07 18:49 ` Ferruh Yigit
2017-11-07 20:47 ` Chas Williams
2017-11-07 22:26 ` Ferruh Yigit
2017-11-08 12:00 ` Chas Williams
2017-11-10 1:40 ` Ferruh Yigit
2017-11-13 23:46 ` Stephen Hemminger
2017-11-07 13:13 ` Stephen Hemminger [this message]
2017-11-07 18:14 ` Chas Williams
2017-11-09 17:20 ` [dpdk-dev] ugb_uio: r3.8xlarge bind failure Gregory Etelson
2017-11-10 1:42 ` Ferruh Yigit
2017-11-10 2:11 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2017-11-10 6:36 ` [dpdk-dev] " Gregory Etelson
2017-11-15 15:44 ` Ferruh Yigit
2017-11-15 16:30 ` Gregory Etelson
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='CAOaVG17Q8NpV5qqRYRK=tjT_0AYESBRrT=jwDAuzqCcLJtKjGA@mail.gmail.com' \
--to=stephen@networkplumber.org \
--cc=3chas3@gmail.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=george.prekas@epfl.ch \
--cc=gregory@weka.io \
--cc=harish.patil@cavium.com \
--cc=jianfeng.tan@intel.com \
--cc=jingjing.wu@intel.com \
--cc=lee.roberts@hpe.com \
--cc=rasesh.mody@cavium.com \
--cc=sergio.gonzalez.monroy@intel.com \
--cc=shijith.thotton@caviumnetworks.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).