From: Russell Coker <russell@coker.com.au>
To: "selinux-refpolicy@vger.kernel.org" <selinux-refpolicy@vger.kernel.org>
Subject: read_file_perms vs mmap_read_file_perms
Date: Sat, 09 Feb 2019 21:25:47 +1100 [thread overview]
Message-ID: <1938152.zeI3LBqMHI@liv> (raw)
define(`read_file_perms',`{ getattr open read lock ioctl }')
define(`mmap_read_file_perms',`{ getattr open map read ioctl }')
I think that the general expectation would be that mmap_read_file_perms is a
superset of read_file_perms. Is there any reason why mmap_read_file_perms
doesn't include lock permission? If not I think we should add it to avoid
surprises.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next reply other threads:[~2019-02-09 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 10:25 Russell Coker [this message]
2019-02-09 14:07 ` read_file_perms vs mmap_read_file_perms Chris PeBenito
2019-02-10 0:04 ` Russell Coker
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=1938152.zeI3LBqMHI@liv \
--to=russell@coker.com.au \
--cc=selinux-refpolicy@vger.kernel.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).