diff options
| author | Vasily Gorbik <gor@linux.ibm.com> | 2020-06-18 17:17:19 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2020-07-16 08:13:34 +0200 |
| commit | 9dae3b787b69947c9270010789142ac6fec6b859 (patch) | |
| tree | 727d0f0f9df5217f01b126a31cc05b59ae5865bf /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 2dcd4768a2b85eca699f049906f22d5cbb83e070 (diff) | |
| download | linux-stable-9dae3b787b69947c9270010789142ac6fec6b859.tar.gz linux-stable-9dae3b787b69947c9270010789142ac6fec6b859.tar.bz2 linux-stable-9dae3b787b69947c9270010789142ac6fec6b859.zip | |
s390/setup: init jump labels before command line parsing
commit 95e61b1b5d6394b53d147c0fcbe2ae70fbe09446 upstream.
Command line parameters might set static keys. This is true for s390 at
least since commit 6471384af2a6 ("mm: security: introduce init_on_alloc=1
and init_on_free=1 boot options"). To avoid the following WARN:
static_key_enable_cpuslocked(): static key 'init_on_alloc+0x0/0x40' used
before call to jump_label_init()
call jump_label_init() just before parse_early_param().
jump_label_init() is safe to call multiple times (x86 does that), doesn't
do any memory allocations and hence should be safe to call that early.
Fixes: 6471384af2a6 ("mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options")
Cc: <stable@vger.kernel.org> # 5.3: d6df52e9996d: s390/maccess: add no DAT mode to kernel_write
Cc: <stable@vger.kernel.org> # 5.3
Reviewed-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions