Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751292AbdFETxQ (ORCPT ); Mon, 5 Jun 2017 15:53:16 -0400 Received: from nm6.bullet.mail.ne1.yahoo.com ([98.138.90.69]:51012 "EHLO nm6.bullet.mail.ne1.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751188AbdFETxP (ORCPT ); Mon, 5 Jun 2017 15:53:15 -0400 X-Yahoo-Newman-Id: 673633.62271.bm@smtp203.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: JbzVVAIVM1lWUZwdZVtTOeH7kpeDcGZR5uMk3iEmVoPiWi4 Po2WBv3L.AjhdOmpWT.dZJJoX869t1vKbyFLGvnXIrI6P6LFROurSNsF.wAI Qqcz5gVzKh_bvnBbqI5Uclvz9IjpdcVHH53J1iu8iOdle3sGx0cHlVJszjGk TvKcK08XXjadX87nS6Kfv2k4O.eFV3VNNfgBosSMYNK2rIpoEcY_KDLf3kFh NHyRSPlvczh1gcsYUtKAaVa.QmPBG07FiSIhNq0weEDYDbXkeoS92JH0_B5A NCM29j2.1dv4u3hXyaC6R_VIlwclxHABIcCcfgwwNyX2clk63okhAN1DbiTC wGKk.IsT.sN7gMq7wBcCktlDHKKqz7uWu_9uXHY_tUaeEOqk92lKj34qlMA8 p1lq634_qnYpMeOiNtX3dQsknP5F5feAbMFD89lJt37qRsLEvsu9eGPD0jPU v00.ypSB.BgtRv8lw1bHp.hqvezDRzpMhHh2cr1E9qzcPxHFSUtpRSdswi1N mIp9jLjmoyrmCXBn4Ob231kbcTAevrQowaoYNp0.l4.H6UDfmIg_Httqfqfw - X-Yahoo-SMTP: OIJXglSswBDfgLtXluJ6wiAYv6_cnw-- Subject: Re: [PATCH 4/5] Make LSM Writable Hooks a command line option To: Igor Stoppa , keescook@chromium.org, mhocko@kernel.org, jmorris@namei.org Cc: penguin-kernel@I-love.SAKURA.ne.jp, paul@paul-moore.com, sds@tycho.nsa.gov, hch@infradead.org, labbott@redhat.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, kernel-hardening@lists.openwall.com References: <20170605192216.21596-1-igor.stoppa@huawei.com> <20170605192216.21596-5-igor.stoppa@huawei.com> From: Casey Schaufler Message-ID: <71e91de0-7d91-79f4-67f0-be0afb33583c@schaufler-ca.com> Date: Mon, 5 Jun 2017 12:53:06 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170605192216.21596-5-igor.stoppa@huawei.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3591 Lines: 122 On 6/5/2017 12:22 PM, Igor Stoppa wrote: > This patch shows how it is possible to take advantage of pmalloc: > instead of using the build-time option __lsm_ro_after_init, to decide if > it is possible to keep the hooks modifiable, now this becomes a > boot-time decision, based on the kernel command line. > > This patch relies on: > > "Convert security_hook_heads into explicit array of struct list_head" > Author: Tetsuo Handa > > to break free from the static constraint imposed by the previous > hardening model, based on __ro_after_init. > > Signed-off-by: Igor Stoppa > CC: Tetsuo Handa > --- > init/main.c | 2 ++ > security/security.c | 29 ++++++++++++++++++++++++++--- > 2 files changed, 28 insertions(+), 3 deletions(-) > > diff --git a/init/main.c b/init/main.c > index f866510..7850887 100644 > --- a/init/main.c > +++ b/init/main.c > @@ -485,6 +485,7 @@ static void __init mm_init(void) > ioremap_huge_init(); > } > > +extern int __init pmalloc_init(void); > asmlinkage __visible void __init start_kernel(void) > { > char *command_line; > @@ -653,6 +654,7 @@ asmlinkage __visible void __init start_kernel(void) > proc_caches_init(); > buffer_init(); > key_init(); > + pmalloc_init(); > security_init(); > dbg_late_init(); > vfs_caches_init(); > diff --git a/security/security.c b/security/security.c > index c492f68..4285545 100644 > --- a/security/security.c > +++ b/security/security.c > @@ -26,6 +26,7 @@ > #include > #include > #include > +#include > #include > > #define MAX_LSM_EVM_XATTR 2 > @@ -33,8 +34,17 @@ > /* Maximum number of letters for an LSM name string */ > #define SECURITY_NAME_MAX 10 > > -static struct list_head hook_heads[LSM_MAX_HOOK_INDEX] > - __lsm_ro_after_init; > +static int security_debug; > + > +static __init int set_security_debug(char *str) > +{ > + get_option(&str, &security_debug); > + return 0; > +} > +early_param("security_debug", set_security_debug); I don't care for calling this "security debug". Making the lists writable after init isn't about development, it's about (Tetsuo's desire for) dynamic module loading. I would prefer "dynamic_module_lists" our something else more descriptive. > + > +static struct list_head *hook_heads; > +static struct pmalloc_pool *sec_pool; > char *lsm_names; > /* Boot-time LSM user choice */ > static __initdata char chosen_lsm[SECURITY_NAME_MAX + 1] = > @@ -59,6 +69,13 @@ int __init security_init(void) > { > enum security_hook_index i; > > + sec_pool = pmalloc_create_pool("security"); > + if (!sec_pool) > + goto error_pool; Excessive gotoing - return -ENOMEM instead. > + hook_heads = pmalloc(sizeof(struct list_head) * LSM_MAX_HOOK_INDEX, > + sec_pool); > + if (!hook_heads) > + goto error_heads; This is the only case where you'd destroy the pool, so the goto is unnecessary. Put the pmalloc_destroy_pool(sec_pool); return -ENOMEM; under the if here. > for (i = 0; i < LSM_MAX_HOOK_INDEX; i++) > INIT_LIST_HEAD(&hook_heads[i]); > pr_info("Security Framework initialized\n"); > @@ -74,8 +91,14 @@ int __init security_init(void) > * Load all the remaining security modules. > */ > do_security_initcalls(); > - > + if (!security_debug) > + pmalloc_protect_pool(sec_pool); > return 0; > + > +error_heads: > + pmalloc_destroy_pool(sec_pool); > +error_pool: > + return -ENOMEM; > } > > /* Save user chosen LSM */