From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Kernel Newbies <kernelnewbies@kernelnewbies.org>
Subject: why are some stat.h "S_*" perm macros not exported via uapi?
Date: Mon, 31 Dec 2018 14:53:30 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.21.1812310748490.17667@localhost.localdomain> (raw)
more pedantry ... just noticed this snippet in include/linux/stat.h:
...
#include <uapi/linux/stat.h>
#define S_IRWXUGO (S_IRWXU|S_IRWXG|S_IRWXO)
#define S_IALLUGO (S_ISUID|S_ISGID|S_ISVTX|S_IRWXUGO)
#define S_IRUGO (S_IRUSR|S_IRGRP|S_IROTH)
#define S_IWUGO (S_IWUSR|S_IWGRP|S_IWOTH)
#define S_IXUGO (S_IXUSR|S_IXGRP|S_IXOTH)
...
given that all of the other S_ perm macros are exported in
include/uapi/linux/stat.h, as in:
#define S_IRWXU 00700
#define S_IRUSR 00400
#define S_IWUSR 00200
#define S_IXUSR 00100
#define S_IRWXG 00070
#define S_IRGRP 00040
#define S_IWGRP 00020
#define S_IXGRP 00010
and so on, is there a reason those few combination perm macros are not
exported as well? or is the userspace stat.h so well-defined at this
point that cosmetic changes like this are frowned upon?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2018-12-31 19:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 19:53 Robert P. J. Day [this message]
2019-01-01 0:44 ` why are some stat.h "S_*" perm macros not exported via uapi? valdis.kletnieks
2019-01-01 9:41 ` Robert P. J. Day
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=alpine.LFD.2.21.1812310748490.17667@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--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).