All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com
Subject: Re: [PATCH] ivshmem: document a potential segmentation fault in rte_ring
Date: Tue, 07 Jun 2016 12:05:27 +0200	[thread overview]
Message-ID: <12418422.MGNHXSpkm5@xps13> (raw)
In-Reply-To: <1464792717-17171-1-git-send-email-anatoly.burakov@intel.com>

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

      reply	other threads:[~2016-06-07 10:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-01 14:51 [PATCH] ivshmem: document a potential segmentation fault in rte_ring Anatoly Burakov
2016-06-07 10:05 ` Thomas Monjalon [this message]

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=12418422.MGNHXSpkm5@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.