From: Oleg Nesterov <oleg@redhat.com>
To: Oleksandr Natalenko <oleksandr@redhat.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-fsdevel@vger.kernel.org, "Jonathan Corbet" <corbet@lwn.net>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Huang Ying" <ying.huang@intel.com>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
"Will Deacon" <will@kernel.org>,
"Guilherme G . Piccoli" <gpiccoli@igalia.com>,
"Laurent Dufour" <ldufour@linux.ibm.com>,
"Stephen Kitt" <steve@sk2.org>, "Rob Herring" <robh@kernel.org>,
"Joel Savitz" <jsavitz@redhat.com>,
"Kees Cook" <keescook@chromium.org>,
"Xiaoming Ni" <nixiaoming@huawei.com>,
"Luis Chamberlain" <mcgrof@kernel.org>,
"Renaud Métrich" <rmetrich@redhat.com>,
"Grzegorz Halat" <ghalat@redhat.com>, "Qi Guo" <qguo@redhat.com>
Subject: Re: [PATCH] core_pattern: add CPU specifier
Date: Wed, 7 Sep 2022 19:34:40 +0200 [thread overview]
Message-ID: <20220907173438.GA15992@redhat.com> (raw)
In-Reply-To: <5599808.DvuYhMxLoT@redhat.com>
On 09/07, Oleksandr Natalenko wrote:
>
> The advantage of having CPU recorded in the file name is that
> in case of multiple cores one can summarise them with a simple
> ls+grep without invoking a fully-featured debugger to find out
> whether the segfaults happened on the same CPU.
Besides, if you only need to gather the statistics about the faulting
CPU(s), you do not even need to actually dump the the core. For example,
something like
#!/usr/bin/sh
echo $* >> path/to/coredump-stat.txt
and
echo '| path-to-script-above %C' >/proc/sys/kernel/core_pattern
can help.
Oleg.
next prev parent reply other threads:[~2022-09-07 17:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 6:43 [PATCH] core_pattern: add CPU specifier Oleksandr Natalenko
2022-09-03 7:20 ` Oleg Nesterov
2022-09-04 18:27 ` Andrew Morton
2022-09-04 19:38 ` Oleg Nesterov
2022-09-06 22:22 ` Eric W. Biederman
2022-09-07 6:15 ` Oleksandr Natalenko
2022-09-07 17:34 ` Oleg Nesterov [this message]
2022-09-07 22:00 ` Eric W. Biederman
2022-09-08 6:11 ` Oleksandr Natalenko
2022-09-07 15:53 ` Luis Chamberlain
2022-09-08 6:45 ` Renaud Métrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220907173438.GA15992@redhat.com \
--to=oleg@redhat.com \
--cc=Jason@zx2c4.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=ebiederm@xmission.com \
--cc=ghalat@redhat.com \
--cc=gpiccoli@igalia.com \
--cc=jsavitz@redhat.com \
--cc=keescook@chromium.org \
--cc=ldufour@linux.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=nixiaoming@huawei.com \
--cc=oleksandr@redhat.com \
--cc=qguo@redhat.com \
--cc=rmetrich@redhat.com \
--cc=robh@kernel.org \
--cc=steve@sk2.org \
--cc=viro@zeniv.linux.org.uk \
--cc=will@kernel.org \
--cc=ying.huang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).