linux-kernel - Re: [PATCH V5 05/13] audit: initialize at subsystem time rather than device time

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20141013123011.GF24703@mail.hallyn.com>
Date:	Mon, 13 Oct 2014 14:30:11 +0200
From:	"Serge E. Hallyn" <serge@...lyn.com>
To:	Richard Guy Briggs <rgb@...hat.com>
Cc:	linux-audit@...hat.com, linux-kernel@...r.kernel.org,
	containers@...ts.linux-foundation.org, eparis@...hat.com,
	sgrubb@...hat.com, aviro@...hat.com, pmoore@...hat.com,
	arozansk@...hat.com, ebiederm@...ssion.com, serge@...lyn.com
Subject: Re: [PATCH V5 05/13] audit: initialize at subsystem time rather than
 device time

Quoting Richard Guy Briggs (rgb@...hat.com):
> The audit subsystem should be initialized a bit earlier so that it is in place
> in time for initial namespace serial number logging.
> ---

Acked-by: Serge Hallyn <serge.hallyn@...onical.com>

>  kernel/audit.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/kernel/audit.c b/kernel/audit.c
> index ff1630d..8ff7f28 100644
> --- a/kernel/audit.c
> +++ b/kernel/audit.c
> @@ -1186,7 +1186,7 @@ static int __init audit_init(void)
>  
>  	return 0;
>  }
> -__initcall(audit_init);
> +subsys_initcall(audit_init);
>  
>  /* Process kernel command-line parameter at boot time.  audit=0 or audit=1. */
>  static int __init audit_enable(char *str)
> -- 
> 1.7.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/