[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220903072018.GA15331@redhat.com>
Date: Sat, 3 Sep 2022 09:20:19 +0200
From: Oleg Nesterov <oleg@...hat.com>
To: Oleksandr Natalenko <oleksandr@...hat.com>
Cc: linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
linux-fsdevel@...r.kernel.org, Jonathan Corbet <corbet@....net>,
Alexander Viro <viro@...iv.linux.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
Huang Ying <ying.huang@...el.com>,
"Jason A . Donenfeld" <Jason@...c4.com>,
Will Deacon <will@...nel.org>,
"Guilherme G . Piccoli" <gpiccoli@...lia.com>,
Laurent Dufour <ldufour@...ux.ibm.com>,
Stephen Kitt <steve@....org>, Rob Herring <robh@...nel.org>,
Joel Savitz <jsavitz@...hat.com>,
"Eric W . Biederman" <ebiederm@...ssion.com>,
Kees Cook <keescook@...omium.org>,
Xiaoming Ni <nixiaoming@...wei.com>,
Luis Chamberlain <mcgrof@...nel.org>,
Renaud Métrich <rmetrich@...hat.com>,
Grzegorz Halat <ghalat@...hat.com>, Qi Guo <qguo@...hat.com>
Subject: Re: [PATCH] core_pattern: add CPU specifier
On 09/03, Oleksandr Natalenko wrote:
>
> Statistically, in a large deployment regular segfaults may indicate a CPU issue.
>
> Currently, it is not possible to find out what CPU the segfault happened on.
> There are at least two attempts to improve segfault logging with this regard,
> but they do not help in case the logs rotate.
>
> Hence, lets make sure it is possible to permanently record a CPU
> the task ran on using a new core_pattern specifier.
>
> Suggested-by: Renaud Métrich <rmetrich@...hat.com>
> Signed-off-by: Oleksandr Natalenko <oleksandr@...hat.com>
> ---
> Documentation/admin-guide/sysctl/kernel.rst | 1 +
> fs/coredump.c | 5 +++++
> include/linux/coredump.h | 1 +
> 3 files changed, 7 insertions(+)
Reviewed-by: Oleg Nesterov <oleg@...hat.com>
Powered by blists - more mailing lists