Message ID | 20190128203056.102178-1-mortonm@chromium.org (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | LSM: Add 'name' field for SafeSetID in DEFINE_LSM | expand |
On Mon, 28 Jan 2019, mortonm@chromium.org wrote: > From: Micah Morton <mortonm@chromium.org> > > Without this, system boot was crashing with: > > [0.174285] LSM: Security Framework initializing > [0.175277] BUG: unable to handle kernel NULL pointer dereference > ... > [0.176272] Call Trace: > [0.176272] ordered_lsm_parse+0x112/0x20b > [0.176272] security_init+0x9b/0x3ab > [0.176272] start_kernel+0x413/0x479 > [0.176272] secondary_startup_64+0xa4/0xb0 > > Signed-off-by: Micah Morton <mortonm@chromium.org> Applied to git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-general
diff --git a/security/safesetid/lsm.c b/security/safesetid/lsm.c index 3a2c75ac810c..282a242beb86 100644 --- a/security/safesetid/lsm.c +++ b/security/safesetid/lsm.c @@ -274,4 +274,5 @@ static int __init safesetid_security_init(void) DEFINE_LSM(safesetid_security_init) = { .init = safesetid_security_init, + .name = "safesetid", };