test suite reviews and discussions
 help / color / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Owen Hilyard <ohilyard@iol.unh.edu>
Cc: dts@dpdk.org, dev <dev@dpdk.org>,
	Lincoln Lavoie <lylavoie@iol.unh.edu>,
	 Aaron Conole <aconole@redhat.com>
Subject: Re: [dts] [dpdk-dev] Userspace testing
Date: Fri, 31 Jul 2020 09:43:44 +0200
Message-ID: <CAJFAV8yf1qXsUW+64Z563QLVNcWquCniAaPEUVfNBe_nKW250g@mail.gmail.com> (raw)
In-Reply-To: <CAHx6DYBhdOzZRbvMUBLDCbfbsuffgqgWAHstvyD1HmP=sj4tGA@mail.gmail.com>

On Wed, Jul 29, 2020 at 4:35 PM Owen Hilyard <ohilyard@iol.unh.edu> wrote:
> I was wondering what everyone's thoughts on doing both userspace testing
> and unprivileged testing of dpdk applications is. DTS currently runs all
> commands on the tester and the dut as the root user. Please correct me if
> I'm wrong, but I was under the assumption that most applications written
> with dpdk would not run as root. This could present a problem since it is
> possible that permissions errors could arise and we wouldn't notice it due
> to the way we currently test. Given that, I was wondering what should and
> should not be possible as a normal (non-root) user, and what would be the
> best way to go about verifying this.

That is an interesting idea.

There are things that won't work unless you give proper permissions
(vfio, hugepages) or capabilities (like for bifurcated solutions: mlx
being the first example that comes to mind).
Additionally, some distributions apply further restrictions, like
SElinux in RHEL. But on this side, I don't think it makes sense, as
selinux rules are distrib specific.

-- 
David Marchand


      parent reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29 14:34 [dts] " Owen Hilyard
     [not found] ` <c70020a2-8948-dda4-bf1f-f5c29ec151b1@intel.com>
2020-07-30 16:54   ` [dts] [dpdk-dev] " Owen Hilyard
     [not found]     ` <bbd7d9a1-09bc-3fc8-b9f1-ab9c71e6c113@intel.com>
2020-08-03 14:31       ` Owen Hilyard
2020-07-31  7:43 ` David Marchand [this message]

Reply instructions:

You may reply publically 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=CAJFAV8yf1qXsUW+64Z563QLVNcWquCniAaPEUVfNBe_nKW250g@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=aconole@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dts@dpdk.org \
    --cc=lylavoie@iol.unh.edu \
    --cc=ohilyard@iol.unh.edu \
    /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

test suite reviews and discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/dts/0 dts/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dts dts/ http://inbox.dpdk.org/dts \
		dts@dpdk.org
	public-inbox-index dts


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dts


AGPL code for this site: git clone https://public-inbox.org/ public-inbox