DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Simon Kagstrom <simon.kagstrom@netinsight.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] mem: Warn once if /proc/self/pagemap is unreadable
Date: Fri, 10 Jul 2015 23:43:45 +0200	[thread overview]
Message-ID: <23551222.oNXA63GnvA@xps13> (raw)
In-Reply-To: <20150624103352.58d20fb3@miho>

2015-06-24 10:33, Simon Kagstrom:
> Newer kernels make this unreadable for security reasons for non-roots.
> Running the application will then fill the logs with
> 
>   rte_mem_virt2phy: cannot open /proc/self/pagemap
> 
> messages.
> 
> However, there are cases when DPDK is and should be run as non-root,
> without the need for virtual-to-physical address translations: a
> typical example is when working with PCAP input/output. This patch
> adds a start-time check for /proc/self/pagemap readability, and
> directly returns an error code from rte_mem_virt2phy().
> 
> This way, there is only a one-time warning at startup instead of
> constant warnings all the time.
> 
> Signed-off-by: Simon Kagstrom <simon.kagstrom@netinsight.net>
> Signed-off-by: Johan Faltstrom <johan.faltstrom@netinsight.net>

Applied, thanks

      reply	other threads:[~2015-07-10 21:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24  8:33 Simon Kagstrom
2015-07-10 21:43 ` 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=23551222.oNXA63GnvA@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=simon.kagstrom@netinsight.net \
    /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).