DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Yoni Gilad <Yonig@radcom.com>
Cc: dev@dpdk.org, Huawei Xie <huawei.xie@intel.com>,
	Yuanhan Liu <yuanhan.liu@linux.intel.com>
Subject: Re: [dpdk-dev] virtio: crash when using multiple processes (16.04 regression)
Date: Thu, 19 May 2016 18:43:19 +0200	[thread overview]
Message-ID: <5703424.Nz7AfLLfu1@xps13> (raw)
In-Reply-To: <DB3PR05MB4919295860E52A070C06A87D54A0@DB3PR05MB491.eurprd05.prod.outlook.com>

2016-05-19 16:20, Yoni Gilad:
> We have encountered a crash in virtio_xmit_pkts (specifically, in the call to virtqueue_notify) when running DPDK in a multi-process setup. This is a regression in DPDK 16.04.

Thanks a lot for reporting.

2 tips to improve such bug report:

- Send it to the maintainer of virtio (and cc this list).
You can find them in the MAINTAINERS file. I've cc'ed them.

- Try to test early the release candidates to have it fixed before
the bug is really released.

> The culprit seems to be the field vtpci_ops in the virtio_hw structure. This field is stored in shared memory, but points to a struct in the primary process's address space. If the same struct was loaded in a different address in the secondary process, it will lead to a crash or other issues when this field is dereferenced there. The referenced virtio_pci_ops struct contains function pointers, which can also be different in the secondary process.

  reply	other threads:[~2016-05-19 16:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-19 16:20 Yoni Gilad
2016-05-19 16:43 ` Thomas Monjalon [this message]
2016-05-23 13:36 ` Yuanhan Liu

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=5703424.Nz7AfLLfu1@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=Yonig@radcom.com \
    --cc=dev@dpdk.org \
    --cc=huawei.xie@intel.com \
    --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).