linux-kernel - Re: [BUG] NULL pointer dereference probably caused by kernel/trace/ring

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] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 1 Nov 2022 18:35:12 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Roland Ruckerbauer <roland.rucky@...il.com>
Cc:     Masami Hiramatsu <mhiramat@...nel.org>,
        linux-kernel@...r.kernel.org, Takashi Iwai <tiwai@...e.de>,
        regressions@...ts.linux.dev,
        Steven Noonan <steven.noonan@...il.com>
Subject: Re: [BUG] NULL pointer dereference probably caused by
 kernel/trace/ring_buffer.c

On Tue, 1 Nov 2022 23:01:38 +0100
Roland Ruckerbauer <roland.rucky@...il.com> wrote:

> Just figured out something, the poll() errors starting at fd 29 (which
> is CPU 24).
> But I only have 24 cores. Looked at
> /sys/kernel/debug/tracing/instances/rasdaemon/per_cpu/, and voila, it
> lists 32 cpus not 24.

Ah, and this explains why I never triggered it. There's some machines
that list nr_cpu_ids as more than what exists (I guess it is "possible
CPUs" and not "actual CPUs").

OK, this is a great clue. I'll dig deeper.

Thanks a lot for telling me this.

Takashi, can you check if the problem machines have more CPUs listed in
/sys/kernel/tracing/per_cpu/cpu* than is on the machine?

-- Steve