From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: russell@coker.com.au, SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: getfscreatecon(3)
Date: Wed, 26 Apr 2006 08:12:13 -0400 [thread overview]
Message-ID: <444F639D.9080709@redhat.com> (raw)
In-Reply-To: <1146051859.28745.16.camel@moss-spartans.epoch.ncsc.mil>
[-- Attachment #1: Type: text/plain, Size: 679 bytes --]
Stephen Smalley wrote:
> On Wed, 2006-04-26 at 13:37 +1000, Russell Coker wrote:
>
>> RETURN VALUE
>> On error -1 is returned.
>>
>> On success getfscreatecon returns the length of the context (not
>> including the trailing zero byte). On success setfscreatecon returns
>> 0.
>>
>>
>> Currently getfscreatecon() returns 0 on success. Should we change the man
>> page or change the library?
>>
>> I think that it would be best to change the library.
>>
>
> The man page should be fixed. Or you'd have to change all of the
> process-oriented get*con functions. As the string is NUL-terminated,
> you don't need the length.
>
>
[-- Attachment #2: diff --]
[-- Type: text/plain, Size: 667 bytes --]
diff --exclude-from=exclude -N -u -r nsalibselinux/man/man3/getfscreatecon.3 libselinux-1.30.3/man/man3/getfscreatecon.3
--- nsalibselinux/man/man3/getfscreatecon.3 2004-05-20 11:32:44.000000000 -0400
+++ libselinux-1.30.3/man/man3/getfscreatecon.3 2006-04-26 08:10:37.000000000 -0400
@@ -32,9 +32,7 @@
save, reset, and restore the fscreate context to avoid unexpected behaviors.
.SH "RETURN VALUE"
On error -1 is returned.
-
-On success getfscreatecon returns the length of the context (not including
-the trailing zero byte). On success setfscreatecon returns 0.
+On success 0 is returned.
.SH "SEE ALSO"
.BR freecon "(3), " getcon "(3), " getexeccon "(3)"
prev parent reply other threads:[~2006-04-26 12:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 3:37 getfscreatecon(3) Russell Coker
2006-04-26 11:44 ` getfscreatecon(3) Stephen Smalley
2006-04-26 12:12 ` Daniel J Walsh [this message]
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=444F639D.9080709@redhat.com \
--to=dwalsh@redhat.com \
--cc=russell@coker.com.au \
--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.