Patch Detail
get:
Show a patch.
patch:
Update a patch.
put:
Update a patch.
GET /api/patches/13145/?format=api
http://patches.dpdk.org/api/patches/13145/?format=api", "web_url": "http://patches.dpdk.org/project/dpdk/patch/1464792717-17171-1-git-send-email-anatoly.burakov@intel.com/", "project": { "id": 1, "url": "http://patches.dpdk.org/api/projects/1/?format=api", "name": "DPDK", "link_name": "dpdk", "list_id": "dev.dpdk.org", "list_email": "dev@dpdk.org", "web_url": "http://core.dpdk.org", "scm_url": "git://dpdk.org/dpdk", "webscm_url": "http://git.dpdk.org/dpdk", "list_archive_url": "https://inbox.dpdk.org/dev", "list_archive_url_format": "https://inbox.dpdk.org/dev/{}", "commit_url_format": "" }, "msgid": "<1464792717-17171-1-git-send-email-anatoly.burakov@intel.com>", "list_archive_url": "https://inbox.dpdk.org/dev/1464792717-17171-1-git-send-email-anatoly.burakov@intel.com", "date": "2016-06-01T14:51:57", "name": "[dpdk-dev] ivshmem: document a potential segmentation fault in rte_ring", "commit_ref": null, "pull_url": null, "state": "accepted", "archived": true, "hash": "dd93cb955e4618c268664683b6ecd0b252dafc08", "submitter": { "id": 4, "url": "http://patches.dpdk.org/api/people/4/?format=api", "name": "Burakov, Anatoly", "email": "anatoly.burakov@intel.com" }, "delegate": { "id": 1, "url": "http://patches.dpdk.org/api/users/1/?format=api", "username": "tmonjalo", "first_name": "Thomas", "last_name": "Monjalon", "email": "thomas@monjalon.net" }, "mbox": "http://patches.dpdk.org/project/dpdk/patch/1464792717-17171-1-git-send-email-anatoly.burakov@intel.com/mbox/", "series": [], "comments": "http://patches.dpdk.org/api/patches/13145/comments/", "check": "pending", "checks": "http://patches.dpdk.org/api/patches/13145/checks/", "tags": {}, "related": [], "headers": { "Return-Path": "<dev-bounces@dpdk.org>", "X-Original-To": "patchwork@dpdk.org", "Delivered-To": "patchwork@dpdk.org", "Received": [ "from [92.243.14.124] (localhost [IPv6:::1])\n\tby dpdk.org (Postfix) with ESMTP id A58B9591F;\n\tWed, 1 Jun 2016 16:52:04 +0200 (CEST)", "from mga04.intel.com (mga04.intel.com [192.55.52.120])\n\tby dpdk.org (Postfix) with ESMTP id 68CE6568B\n\tfor <dev@dpdk.org>; Wed, 1 Jun 2016 16:52:01 +0200 (CEST)", "from orsmga003.jf.intel.com ([10.7.209.27])\n\tby fmsmga104.fm.intel.com with ESMTP; 01 Jun 2016 07:51:59 -0700", "from irvmail001.ir.intel.com ([163.33.26.43])\n\tby orsmga003.jf.intel.com with ESMTP; 01 Jun 2016 07:51:58 -0700", "from sivswdev02.ir.intel.com (sivswdev02.ir.intel.com\n\t[10.237.217.46])\n\tby irvmail001.ir.intel.com (8.14.3/8.13.6/MailSET/Hub) with ESMTP id\n\tu51Epve3025663; Wed, 1 Jun 2016 15:51:57 +0100", "from sivswdev02.ir.intel.com (localhost [127.0.0.1])\n\tby sivswdev02.ir.intel.com with ESMTP id u51EpvYB017208;\n\tWed, 1 Jun 2016 15:51:57 +0100", "(from aburakov@localhost)\n\tby sivswdev02.ir.intel.com with id u51Epv4t017204;\n\tWed, 1 Jun 2016 15:51:57 +0100" ], "X-ExtLoop1": "1", "X-IronPort-AV": "E=Sophos;i=\"5.26,401,1459839600\"; d=\"scan'208\";a=\"819401471\"", "From": "Anatoly Burakov <anatoly.burakov@intel.com>", "To": "dev@dpdk.org", "Cc": "ferruh.yigit@intel.com", "Date": "Wed, 1 Jun 2016 15:51:57 +0100", "Message-Id": "<1464792717-17171-1-git-send-email-anatoly.burakov@intel.com>", "X-Mailer": "git-send-email 1.7.4.1", "Subject": "[dpdk-dev] [PATCH] ivshmem: document a potential segmentation fault\n\tin rte_ring", "X-BeenThere": "dev@dpdk.org", "X-Mailman-Version": "2.1.15", "Precedence": "list", "List-Id": "patches and discussions about DPDK <dev.dpdk.org>", "List-Unsubscribe": "<http://dpdk.org/ml/options/dev>,\n\t<mailto:dev-request@dpdk.org?subject=unsubscribe>", "List-Archive": "<http://dpdk.org/ml/archives/dev/>", "List-Post": "<mailto:dev@dpdk.org>", "List-Help": "<mailto:dev-request@dpdk.org?subject=help>", "List-Subscribe": "<http://dpdk.org/ml/listinfo/dev>,\n\t<mailto:dev-request@dpdk.org?subject=subscribe>", "Errors-To": "dev-bounces@dpdk.org", "Sender": "\"dev\" <dev-bounces@dpdk.org>" }, "content": "Commit 4768c475 added a pointer to the memzone in rte_ring. However,\nall memzones are residing in local mem_config, therefore accessing\nthe memzone pointer inside the guest in an IVSHMEM-shared rte_ring\nwill cause segmentation fault. This issue is unlikely to ever get\nfixed, as this would require lots of changes for very little benefit,\ntherefore we're documenting this limitation instead.\n\nSigned-off-by: Anatoly Burakov <anatoly.burakov@intel.com>\n---\n doc/guides/prog_guide/ivshmem_lib.rst | 2 ++\n 1 file changed, 2 insertions(+)", "diff": "diff --git a/doc/guides/prog_guide/ivshmem_lib.rst b/doc/guides/prog_guide/ivshmem_lib.rst\nindex 9401ccf..b8a32e4 100644\n--- a/doc/guides/prog_guide/ivshmem_lib.rst\n+++ b/doc/guides/prog_guide/ivshmem_lib.rst\n@@ -79,6 +79,8 @@ The following is a simple guide to using the IVSHMEM Library API:\n Only data structures fully residing in DPDK hugepage memory work correctly.\n Supported data structures created by malloc(), mmap()\n or otherwise using non-DPDK memory cause undefined behavior and even a segmentation fault.\n+ Specifically, because the memzone field in an rte_ring refers to a memzone structure residing in local memory,\n+ accessing the memzone field in a shared rte_ring will cause an immediate segmentation fault.\n \n IVSHMEM Environment Configuration\n ---------------------------------\n", "prefixes": [ "dpdk-dev" ] }{ "id": 13145, "url": "