From: Jeffrey Walton <noloader@gmail.com>
To: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: SElinux and its own error code?
Date: Sat, 2 May 2020 23:55:02 -0400 [thread overview]
Message-ID: <CAH8yC8kjRr29R8=zeUuyE5NKVDMZsdHMh+Z9a9mgP51VWYu-jQ@mail.gmail.com> (raw)
Hi Guys,
I lost about four hours chasing inaccurate messages from Apache. It
turns out SElinux was denying access, so the EPERM was not really
accurate. But Apache saw EPERM or EACCESS and logged a message related
to Posix permissions.
As far as I know Posix does not authorize use of EPERM or EACCESS for
SElinux. That is, SElinux should not be hijacking the error code.
I'm wondering why there is no error message for SElinux that would
allow application to return a specific error when SElinux denies
access to an object or operation.
Why does SElinux not have its own error code?
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2020-05-03 3:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 3:55 Jeffrey Walton [this message]
2020-05-03 7:45 ` SElinux and its own error code? Greg KH
2020-05-03 7:50 ` Valdis Klētnieks
2020-05-03 7:59 ` Jeffrey Walton
2020-05-03 9:18 ` Greg KH
2020-05-03 16:02 ` Bernd Petrovitsch
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='CAH8yC8kjRr29R8=zeUuyE5NKVDMZsdHMh+Z9a9mgP51VWYu-jQ@mail.gmail.com' \
--to=noloader@gmail.com \
--cc=kernelnewbies@kernelnewbies.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).