From: Sam Ravnborg <sam@ravnborg.org>
To: John Johansen <john.johansen@canonical.com>,
James Morris <jmorris@namei.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Comments to apparmor Makefile (and security/Makefile)
Date: Sat, 28 Aug 2010 09:03:05 +0200 [thread overview]
Message-ID: <20100828070305.GA8842@merkur.ravnborg.org> (raw)
Hi John.
I took a closer at security/apparmor/Makefile.
And I got a few comments...
1) You have in the bottom explicit rules for three files:
capability_names.h, rlim_names.h and af_names.h
But the altter file is not referenced in any
apparmor file.
And there is no cmd_make-af variable defined.
Looks like a leftover that shall be dropped.
2) clean-files fails to include rlim_names.h
3) The cmd_make-caps line is much too long.
Please use "\" to break lines in smaller logical parts.
Same goes with the other cdm_ line.
4) make-rlim delete the symbol AF_MAX - but that does not
exist in the input file.
5) Two of the sed expressions looks almost equal - should they have been equal?
6) A small comment describing the purpose of each sed expression would be helpfull
Something like:
# Transform lines from:
# #define FOO 123
# =>
# #define RLIM_FOO 123
7) af_names.h needs to be dropped in .gitignore
8) From security/Makefile:
obj-$(CONFIG_SECURITY_APPARMOR) += apparmor/built-in.o
This is _not_ how we do it.
We say just:
obj-$(CONFIG_SECURITY_APPARMOR) += apparmor/
[security/Makefile has this issue in several places]
There was a few tings that made me unsafe just providing a patch,
so for now you got a list of comments.
Sam
next reply other threads:[~2010-08-28 7:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-28 7:03 Sam Ravnborg [this message]
2010-08-28 19:11 ` John Johansen
2010-08-28 19:21 ` Sam Ravnborg
2010-08-28 20:32 ` John Johansen
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=20100828070305.GA8842@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--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®