public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Kentaro Takeda <takedakn@nttdata.co.jp>,
	Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
	tomoyo-dev-en@lists.sourceforge.jp,
	James Morris <jmorris@namei.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH] security: TOMOYO should clean policy files
Date: Tue, 14 Feb 2012 13:06:42 -0800	[thread overview]
Message-ID: <4F3ACCE2.6040200@xenotime.net> (raw)

From: Randy Dunlap <rdunlap@xenotime.net>

TOMOYO creates some empty/default policy files during build.
It should remove them during 'make clean'.

I noticed that they were not being removed because the
"Creating ..." messages always occurred a maximum of one time
during 25 randconfig builds, so it was sometimes using the
files from a previous build (which is not a problem, but
still, 'make clean' should remove them).

Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
Cc:	Kentaro Takeda <takedakn@nttdata.co.jp>
Cc:	Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc:	tomoyo-dev-en@lists.sourceforge.jp
---
 security/tomoyo/Makefile |    2 ++
 1 file changed, 2 insertions(+)

--- linux-next-20120214.orig/security/tomoyo/Makefile
+++ linux-next-20120214/security/tomoyo/Makefile
@@ -46,3 +46,5 @@ $(obj)/builtin-policy.h: $(obj)/policy/p
 	@mv $@.tmp $@
 
 $(obj)/common.o: $(obj)/builtin-policy.h
+
+clean-dirs := $(objtree)/security/tomoyo/policy/

             reply	other threads:[~2012-02-14 21:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-14 21:06 Randy Dunlap [this message]
2012-02-15 12:36 ` [PATCH] security: TOMOYO should clean policy files Tetsuo Handa

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=4F3ACCE2.6040200@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=akpm@linux-foundation.org \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=takedakn@nttdata.co.jp \
    --cc=tomoyo-dev-en@lists.sourceforge.jp \
    /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