From: Steve G <linux_4ever@yahoo.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Daniel J Walsh <dwalsh@redhat.com>, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: libselinux patch
Date: Wed, 21 Feb 2007 06:03:52 -0800 (PST) [thread overview]
Message-ID: <948733.27387.qm@web51508.mail.yahoo.com> (raw)
In-Reply-To: <1172065357.14363.273.camel@moss-spartans.epoch.ncsc.mil>
>> >At present, libselinux dynamically determines where selinuxfs is mounted
>> >via /proc/mounts in init_selinuxmnt() and uses that path for all calls
>> >that operate on selinuxfs.
>>
>> I guess that path could be used for statfs?
>
>That still leaves you with a dependency on successfully
>reading /proc/mounts and allocating memory, so no different than
>reading /proc/filesystems as far as robustness goes.
Actually, you could guess "/selinux" and drop back to dynamically determining if
that failed. that would get that call down to 1 syscall, too. I'd say 99.99% of
the time it would be the right guess. Only at boot, shutdown, or a strange chroot
config would there be a possibility of something different.
>is_selinux_enabled() should never be on a critical path (should
>always be called during startup by a program and saved for later
>use in a variable).
Every selinux aware app checks it and it could short circuit seeveral syscalls to
get the right answer.
-Steve
____________________________________________________________________________________
TV dinner still cooling?
Check out "Tonight's Picks" on Yahoo! TV.
http://tv.yahoo.com/
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2007-02-21 14:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 14:31 libselinux patch Daniel J Walsh
2007-02-20 15:05 ` Steve G
2007-02-20 15:06 ` Stephen Smalley
2007-02-21 13:12 ` Steve G
2007-02-21 13:20 ` Stephen Smalley
2007-02-21 13:37 ` Steve G
2007-02-21 13:42 ` Stephen Smalley
2007-02-21 14:03 ` Steve G [this message]
2007-02-21 18:26 ` Steve G
2007-02-22 12:34 ` Stephen Smalley
2007-02-22 13:46 ` Steve G
2007-02-22 14:10 ` Stephen Smalley
2007-02-22 15:48 ` Steve G
2007-02-23 20:45 ` Stephen Smalley
2007-02-26 16:40 ` Steve G
2007-02-27 15:15 ` Stephen Smalley
2007-02-27 15:58 ` Christopher J. PeBenito
2007-02-22 14:45 ` James Antill
2007-02-21 14:47 ` Stefanos Harhalakis
2007-02-21 17:21 ` Stephen Smalley
-- strict thread matches above, loose matches on Subject: below --
2007-04-05 17:25 Daniel J Walsh
2007-04-05 17:44 ` Stephen Smalley
2007-04-05 21:00 ` Daniel J Walsh
2007-04-09 14:17 ` Stephen Smalley
2007-04-09 15:12 ` Daniel J Walsh
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=948733.27387.qm@web51508.mail.yahoo.com \
--to=linux_4ever@yahoo.com \
--cc=dwalsh@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.