DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Robin Jarry <robin.jarry@6wind.com>
Cc: dev@dpdk.org, sergio.gonzalez.monroy@intel.com
Subject: Re: [dpdk-dev] [PATCH] eal/linux: use more restrictive perms in hugedir
Date: Fri, 16 Sep 2016 14:51:19 +0200	[thread overview]
Message-ID: <3033732.gf2zZdh5yM@xps13> (raw)
In-Reply-To: <1470840774-14793-1-git-send-email-robin.jarry@6wind.com>

2016-08-10 16:52, Robin Jarry:
> There is no need for the page files to be readable (and executable) by
> other users. This can be exploited by non-privileged users to access the
> working memory of a DPDK app.
> 
> Open the files with 0600.
> 
> Signed-off-by: Robin Jarry <robin.jarry@6wind.com>

Applied, thanks

I thought there were some comments about this.
Tip of the day: August is a good month to avoid comments on your patch ;)

      reply	other threads:[~2016-09-16 12:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 14:52 Robin Jarry
2016-09-16 12:51 ` 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=3033732.gf2zZdh5yM@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=robin.jarry@6wind.com \
    --cc=sergio.gonzalez.monroy@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).