From: Joe Perches <joe@perches.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] proc: Convert S_<FOO> permission uses to octal
Date: Fri, 12 Feb 2021 16:39:25 -0800 [thread overview]
Message-ID: <0c276a12b04d8078dc3a22e57b4f41547178329f.camel@perches.com> (raw)
In-Reply-To: <m1y2fszwa7.fsf@fess.ebiederm.org>
On Fri, 2021-02-12 at 17:44 -0600, Eric W. Biederman wrote:
> I certainly do not see sufficient consensus to go around changing code
> other people maintain.
Every patch by a non-maintainer that doesn't have commit rights to
whatever tree is just a proposal.
> My suggest has the nice property that it handles all 512 different
> combinations. I think that was the only real downside of Ingo's
> suggestion. There are just too many different combinations to define
> a set of macros to cover all of the cases.
The treewide kernel use of octal vs symbolic permissions is ~2:1
There are about 11k uses of 4 digit octal values used for permissions
already in the kernel sources that are not in comments or strings.
$ git ls-files -- '*.[ch]' | xargs scc | sed 's/".*"//g' | grep -P -w '0[0-7]{3,3}' | wc -l
10818
(scc is a utility tool that strips comments from c source
see: https://github.com/jleffler/scc-snapshots#readme)
vs:
$ git grep -w -P 'S_I[RWX][A-Z]{3,5}' | wc -l
5247
To my knowledge there just aren't many 4 digit octal uses in the
kernel sources that are _not_ permissions.
I believe the only non-permission 4 digit octal int uses not in
comments are:
include/uapi/linux/a.out.h
#define OMAGIC 0407
#define NMAGIC 0410
#define ZMAGIC 0413
#define QMAGIC 0314
#define CMAGIC 0421
#define N_STAB 0340
include/uapi/linux/coff.h
#define COFF_STMAGIC 0401
#define COFF_OMAGIC 0404
#define COFF_JMAGIC 0407
#define COFF_DMAGIC 0410
#define COFF_ZMAGIC 0413
#define COFF_SHMAGIC 0443
fs/binfmt_flat.c:
if ((buf[0] != 037) || ((buf[1] != 0213) && (buf[1] != 0236))) {
lib/inflate.c:
((magic[1] != 0213) && (magic[1] != 0236))) {
And maybe those last 2 tests for gzip identification should be combined
into some static inline and use something other than magic constants.
next prev parent reply other threads:[~2021-02-13 0:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 19:11 Joe Perches
2021-02-12 22:01 ` Eric W. Biederman
2021-02-12 22:19 ` Matthew Wilcox
2021-02-12 23:48 ` Eric W. Biederman
2021-02-13 0:42 ` Joe Perches
2021-02-12 22:51 ` Joe Perches
2021-02-12 23:44 ` Eric W. Biederman
2021-02-13 0:39 ` Joe Perches [this message]
2021-02-13 8:02 ` Alexey Dobriyan
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=0c276a12b04d8078dc3a22e57b4f41547178329f.camel@perches.com \
--to=joe@perches.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®