DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Tan, Jianfeng" <jianfeng.tan@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"yuanhan.liu@linux.intel.com" <yuanhan.liu@linux.intel.com>,
	"maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>
Subject: Re: [dpdk-dev] [PATCH] eal: fix secondary process segfault on multipe virtio devices
Date: Mon, 3 Jul 2017 08:38:42 +0000	[thread overview]
Message-ID: <ED26CBA2FAD1BF48A8719AEF02201E36512226E8@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <34094937.BVuX3fK5it@xps>

HI Thomas,


> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Saturday, July 1, 2017 10:10 PM
> To: Tan, Jianfeng
> Cc: dev@dpdk.org; yuanhan.liu@linux.intel.com;
> maxime.coquelin@redhat.com
> Subject: Re: [dpdk-dev] [PATCH] eal: fix secondary process segfault on
> multipe virtio devices
> 
> 02/06/2017 18:20, Jianfeng Tan:
> > Suppose we have 2 virtio devices for a VM, with only the first one,
> > virtio0, binding to igb_uio. Start a primary DPDK process, driving
> > only virtio0. Then start a secondary DPDK process, it encounters
> > segfault at eth_virtio_dev_init() because hw is NULL, when trying
> > to initialize the 2nd virtio devices.
> >     1539                    if (!hw->virtio_user_dev) {
> >
> > We could add a precheck to return error when hw is NULL. But the
> > root cause is that virtio devices which are not driven by the primary
> > process are not exluded by secondary eal probe function.
> >
> > To support legacy virtio devices bound to none kernel driver, we
> > removed RTE_PCI_DRV_NEED_MAPPING in
> > commit 962cf902e6eb ("pci: export device mapping functions").
> > At the boot of primary process, ether dev is allocated in rte_eth_devices
> > array, rte_eth_dev_data is also allocated in rte_eth_dev_data array; then
> > probe function fails; and ether dev is released. However, the entry in
> > rte_eth_dev_data array is not cleared. Then we start secondary process,
> > and try to attach the virtio device that not used in primary process,
> > the field, dev_private (or hw), in rte_eth_dev_data, is NULL.
> >
> > To fail the dev attach, we need to clear the field, name, when we
> > release any ether devices in primary, so that below loop in
> > rte_eth_dev_attach_secondary() will not find any matched names.
> >         for (i = 0; i < RTE_MAX_ETHPORTS; i++) {
> >                 if (strcmp(rte_eth_dev_data[i].name, name) == 0)
> >                         break;
> >         }
> >
> > Fixes: 6d890f8ab512 ("Fixes: net/virtio: fix multiple process support")
> 
> It probably needs to be Cc: stable@dpdk.org
> 
> > Reported-by: Reshma Pattan <reshma.pattan@intel.com>
> > Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com>
> > ---
> [...]
> >  	eth_dev->data->dev_private = NULL;
> >
> > +	/* Secondary process will use this field, name, for secondary attach,
> > +	 * clear this field to avoid attaching any released ports in primary.
> > +	 */
> > +	memset(eth_dev->data->name, 0, RTE_ETH_NAME_MAX_LEN);
> 
> I think it may be sufficient to set an empty string:
> eth_dev->data->name = '\0';

Thank you for the advice. And a new version has been sent.

Thanks,
Jianfeng

  reply	other threads:[~2017-07-03  8:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02 16:20 Jianfeng Tan
2017-07-01 14:10 ` Thomas Monjalon
2017-07-03  8:38   ` Tan, Jianfeng [this message]
2017-07-03  6:37 ` [dpdk-dev] [PATCH v2] " Jianfeng Tan
2017-07-05 10:11   ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon

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=ED26CBA2FAD1BF48A8719AEF02201E36512226E8@SHSMSX103.ccr.corp.intel.com \
    --to=jianfeng.tan@intel.com \
    --cc=dev@dpdk.org \
    --cc=maxime.coquelin@redhat.com \
    --cc=thomas@monjalon.net \
    --cc=yuanhan.liu@linux.intel.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).