linux-kernel - Re: [PATCH] tracing: Make the space reserved for the pid wider

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 15 Sep 2020 09:05:20 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc:     linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] tracing: Make the space reserved for the pid wider

On Tue, 15 Sep 2020 12:46:48 +0200
Sebastian Andrzej Siewior <bigeasy@...utronix.de> wrote:

> On 2020-09-04 10:23:31 [+0200], To linux-kernel@...r.kernel.org wrote:
> > For 64bit CONFIG_BASE_SMALL=0 systems PID_MAX_LIMIT is set by default to
> > 4194304. During boot the kernel sets a new value based on number of CPUs
> > but no lower than 32768. It is 1024 per CPU so with 128 CPUs the default
> > becomes 131072 which needs six digits. 
> > This value can be increased during run time but must not exceed the
> > initial upper limit.
> > 
> > Systemd sometime after v241 sets it to the upper limit during boot. The
> > result is that when the pid exceeds five digits, the trace output is a
> > little hard to read because it is no longer properly padded (same like
> > on big iron with 98+ CPUs).
> > 
> > Increase the pid padding to seven digits.  
> 
> ping
> 

Hi Sebastian,

I'm still buried in email from my PTO, with lots of patches I need to
review and apply (or comment on). And I'm also behind in internal work
affairs. I'm not ignoring this, just taking some time to get to it :-/

-- Steve