Skip to contentSkip to conversation

security: TOMOYO should clean policy files

PATCH In review Randy Dunlap 2 participants 2 messages Feb 14, 2012 – Feb 15, 2012

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 security: TOMOYO should clean policy files

From: Randy Dunlap <[email protected]>

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).

---
 security/tomoyo/Makefile |    2 ++
 1 file changed, 2 insertions(+)
security/tomoyo/Makefile +2 -0
@@ -46,3 +46,5 @@ $(obj)/builtin-policy.h: $(obj)/policy/p
 	@mv [email protected] $@
 
 $(obj)/common.o: $(obj)/builtin-policy.h
+
+clean-dirs := $(objtree)/security/tomoyo/policy/
maintainer
#1 lore raw
Quoted 8 lines · Randy Dunlap

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).

Thank you. But I prefer current behavior.

The content of automatically generated files depends on neither kernel config nor architecture. They are static contents which are used when a user did not explicitly supply contents. Therefore, I think we don't need to delete them by 'make clean'.