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] [day] [month] [year] [list]
Message-Id: <20260118124434.1373ffe0f314019381257a7f@linux-foundation.org>
Date: Sun, 18 Jan 2026 12:44:34 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Pnina Feder <pnina.feder@...ileye.com>
Cc: pmladek@...e.com, bhe@...hat.com, linux-kernel@...r.kernel.org,
 lkp@...el.com, mgorman@...e.de, mingo@...hat.com, peterz@...radead.org,
 rostedt@...dmis.org, senozhatsky@...omium.org, tglx@...utronix.de,
 vkondra@...ileye.com
Subject: Re: [PATCH v1] panic: add panic_redirect_cpu declaration to header

On Sun, 18 Jan 2026 14:01:49 +0200 Pnina Feder <pnina.feder@...ileye.com> wrote:

> Add the extern declaration for panic_redirect_cpu to linux/panic.h
> to fix the sparse warning:
> 
>   kernel/panic.c:305:10: sparse: sparse: symbol 'panic_redirect_cpu'
>   was not declared. Should it be static?
> 
> The variable needs to be declared in the header alongside panic_cpu
> since it is used for synchronization when redirecting panic to a
> specific CPU via the panic_force_cpu= boot parameter.
> 

Thanks, I added this as a squashable fix against your earlier patch
"panic: add panic_force_cpu= parameter to redirect panic to a specific
CPU".

(It's nice to tell people when a patch fixes a pending patch in this
manner - otherwise everyone has to run around trying to figure out
which tree is being patched and why).

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ