Messages in this thread | | | From | Paul Gortmaker <> | Subject | [PATCH 0/2] security: clarify that some code is really non-modular | Date | Wed, 9 Dec 2015 17:37:14 -0500 |
| |
The goal is to ensure that non-modular code doesn't appear modular just by accident. Here we have two more commits to do that and they are of the trivial nature (i.e. no ".remove" functions deleted and no need to block any unbind actions). We just change the registration functions to be the non modular versions and adjust the include headers to match.
Paul Gortmaker (2): security/keys: make big_key.c explicitly non-modular security/integrity: make ima/ima_mok.c explicitly non-modular
security/integrity/ima/ima_mok.c | 5 ++--- security/keys/big_key.c | 15 +-------------- 2 files changed, 3 insertions(+), 17 deletions(-)
---
Cc: David Howells <dhowells@redhat.com> Cc: James Morris <james.l.morris@oracle.com> Cc: "Serge E. Hallyn" <serge@hallyn.com> Cc: keyrings@linux-nfs.org Cc: linux-security-module@vger.kernel.org Cc: Mimi Zohar <zohar@linux.vnet.ibm.com> Cc: Dmitry Kasatkin <dmitry.kasatkin@gmail.com> Cc: James Morris <james.l.morris@oracle.com> Cc: "Serge E. Hallyn" <serge@hallyn.com> Cc: linux-ima-devel@lists.sourceforge.net Cc: linux-ima-user@lists.sourceforge.net Cc: linux-security-module@vger.kernel.org
2.6.1
| |