On Sat, 3 Sep 2022 08:43:30 +0200 Oleksandr Natalenko <oleksandr@xxxxxxxxxx> 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. > > ... > > } > @@ -535,6 +539,7 @@ void do_coredump(const kernel_siginfo_t *siginfo) > */ > .mm_flags = mm->flags, > .vma_meta = NULL, > + .cpu = raw_smp_processor_id(), > }; Why use the "raw_" function here?
