DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] [PATCH] ivshmem: document a potential segmentation fault in rte_ring
@ 2016-06-01 14:51 Anatoly Burakov
  2016-06-07 10:05 ` Thomas Monjalon
  0 siblings, 1 reply; 2+ messages in thread
From: Anatoly Burakov @ 2016-06-01 14:51 UTC (permalink / raw)
  To: dev; +Cc: ferruh.yigit

Commit 4768c475 added a pointer to the memzone in rte_ring. However,
all memzones are residing in local mem_config, therefore accessing
the memzone pointer inside the guest in an IVSHMEM-shared rte_ring
will cause segmentation fault. This issue is unlikely to ever get
fixed, as this would require lots of changes for very little benefit,
therefore we're documenting this limitation instead.

Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
---
 doc/guides/prog_guide/ivshmem_lib.rst | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/doc/guides/prog_guide/ivshmem_lib.rst b/doc/guides/prog_guide/ivshmem_lib.rst
index 9401ccf..b8a32e4 100644
--- a/doc/guides/prog_guide/ivshmem_lib.rst
+++ b/doc/guides/prog_guide/ivshmem_lib.rst
@@ -79,6 +79,8 @@ The following is a simple guide to using the IVSHMEM Library API:
     Only data structures fully residing in DPDK hugepage memory work correctly.
     Supported data structures created by malloc(), mmap()
     or otherwise using non-DPDK memory cause undefined behavior and even a segmentation fault.
+    Specifically, because the memzone field in an rte_ring refers to a memzone structure residing in local memory,
+    accessing the memzone field in a shared rte_ring will cause an immediate segmentation fault.
 
 IVSHMEM Environment Configuration
 ---------------------------------
-- 
2.5.0

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [dpdk-dev] [PATCH] ivshmem: document a potential segmentation fault in rte_ring
  2016-06-01 14:51 [dpdk-dev] [PATCH] ivshmem: document a potential segmentation fault in rte_ring Anatoly Burakov
@ 2016-06-07 10:05 ` Thomas Monjalon
  0 siblings, 0 replies; 2+ messages in thread
From: Thomas Monjalon @ 2016-06-07 10:05 UTC (permalink / raw)
  To: Anatoly Burakov; +Cc: dev, ferruh.yigit

2016-06-01 15:51, Anatoly Burakov:
> Commit 4768c475 added a pointer to the memzone in rte_ring. However,
> all memzones are residing in local mem_config, therefore accessing
> the memzone pointer inside the guest in an IVSHMEM-shared rte_ring
> will cause segmentation fault. This issue is unlikely to ever get
> fixed, as this would require lots of changes for very little benefit,
> therefore we're documenting this limitation instead.
> 
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>

Applied, thanks

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2016-06-07 10:05 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-06-01 14:51 [dpdk-dev] [PATCH] ivshmem: document a potential segmentation fault in rte_ring Anatoly Burakov
2016-06-07 10:05 ` Thomas Monjalon

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).