DPDK usage discussions
 help / color / mirror / Atom feed
From: "Lazarenko, Vlad (WorldQuant)" <Vlad.Lazarenko@worldquant.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] KNI & SIOCSIFFLAGS permission?
Date: Mon, 13 Feb 2017 16:26:43 +0000	[thread overview]
Message-ID: <790E2AC11206AC46B8F4BB82078E34F80628342B@EXUSMBX02.AD.MLP.com> (raw)

Howdy,

When using KNI, I'm trying to programmatically enable the port by bringing the interface up by calling ioctl with SIOCGIFFLAGS (thanks Dumitru Caera and Juniper's warp17 for great help getting KNI wrapped in PMD the right way!). However, kernel does not allow me to do this unless I am root or the executable has CAP_NET_ADMIN capability. Warp17 suggests to change user of the executable to root and give it SUI bit. Needless to say that configuring capabilities or running my process as root is a pain in the neck. So the question is how do you guys usually go about this? Also, since we already have access to rte_kni.ko, can we somehow add code there to enable us to bypass this kernel permission check just to make life easier?

Thanks,
Vlad



###################################################################################

The information contained in this communication is confidential, may be

subject to legal privilege, and is intended only for the individual named.

If you are not the named addressee, please notify the sender immediately and

delete this email from your system.  The views expressed in this email are

the views of the sender only.  Outgoing and incoming electronic communications

to this address are electronically archived and subject to review and/or disclosure

to someone other than the recipient.

###################################################################################

                 reply	other threads:[~2017-02-13 16:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=790E2AC11206AC46B8F4BB82078E34F80628342B@EXUSMBX02.AD.MLP.com \
    --to=vlad.lazarenko@worldquant.com \
    --cc=users@dpdk.org \
    /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).