From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, stable@dpdk.org,
Boris Ouretskey <borisusun@gmail.com>,
Isaac Boukris <iboukris@gmail.com>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH] doc: add capability to access physical addresses
Date: Sun, 15 Jan 2023 15:46:06 +0300 [thread overview]
Message-ID: <20230115154606.31e855cf@sovereign> (raw)
In-Reply-To: <20230114182752.0fa60bf7@hermes.local>
2023-01-14 18:27 (UTC-0800), Stephen Hemminger:
> DAC_OVERRIDE is like having the master key. It opens all doors
> and if so, running as non-root really doesn't matter that much.
>
> Ideally, a finer grain permission could be used.
> Recommending this to users seems wrong.
According to my tests, DAC_READ_SEARCH can be used instead of DAC_OVERRIDE.
It seems slightly better, because it doesn't bypass write permission checks.
Although I agree with Isaac that SYS_ADMIN is already very powerful,
and remember that the final goal is to perform unrestricted DMA.
Boris, Isaac, is DAC_READ_SEARCH sufficient on your systems?
next prev parent reply other threads:[~2023-01-15 12:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 22:58 Dmitry Kozlyuk
2023-01-15 2:27 ` Stephen Hemminger
2023-01-15 6:20 ` Isaac Boukris
2023-01-15 12:46 ` Dmitry Kozlyuk [this message]
2023-01-15 13:30 ` Isaac Boukris
2023-01-19 21:24 Dmitry Kozlyuk
2023-03-28 19:19 ` Thomas Monjalon
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=20230115154606.31e855cf@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=borisusun@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=iboukris@gmail.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.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).