From: Justin Cormack <justin@specialbusservice.com>
To: musl@lists.openwall.com
Subject: unexpected syscall failures
Date: Tue, 16 Apr 2013 09:02:31 +0100 [thread overview]
Message-ID: <CAK4o1WyB+mfLTLvnyroQd6qtppSU9m98=aWVDs8+6FHqfA4ncg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 749 bytes --]
I noticed that in some places we assume some system calls will not fail,
one example being in nice that I was looking at the other day, but there
are others:
return setpriority(PRIO_PROCESS, 0, getpriority(PRIO_PROCESS, 0)+inc);
Now in Linux you can use security frameworks (eg type 2 seccomp) to make
any system call fail. Do we want to program defensively around these cases?
(In the case of seccomp I think most people use it to abort the program not
error, but you can).
I am inclined to think that if someone makes getpid fail they deserve
anything they get. I can't see any security issues, just some potentially
confusing behaviour, eg here nice might succeed (but set errno) if
getpriority fails. But testing does have downsides.
Justin
[-- Attachment #2: Type: text/html, Size: 1319 bytes --]
next reply other threads:[~2013-04-16 8:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 8:02 Justin Cormack [this message]
2013-04-17 1:14 ` Rich Felker
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='CAK4o1WyB+mfLTLvnyroQd6qtppSU9m98=aWVDs8+6FHqfA4ncg@mail.gmail.com' \
--to=justin@specialbusservice.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).