linux-hardening - Re: [PATCH] printk: add cpu id information to printk() output

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: Fri, 22 Sep 2023 15:34:44 +0800
From: Enlin Mu <enlinmu@...il.com>
To: John Ogness <john.ogness@...utronix.de>
Cc: Enlin Mu <enlin.mu@...look.com>, pmladek@...e.com, rostedt@...dmis.org, 
	senozhatsky@...omium.org, keescook@...omium.org, tony.luck@...el.com, 
	gpiccoli@...lia.com, enlin.mu@...soc.com, linux-kernel@...r.kernel.org, 
	linux-hardening@...r.kernel.org
Subject: Re: [PATCH] printk: add cpu id information to printk() output

John Ogness <john.ogness@...utronix.de> 于2023年9月15日周五 16:34写道：
>
> On 2023-09-15, Enlin Mu <enlin.mu@...look.com> wrote:
> > Sometimes we want to print cpu id of printk() messages to consoles
> >
> > diff --git a/include/linux/threads.h b/include/linux/threads.h
> > index c34173e6c5f1..6700bd9a174f 100644
> > --- a/include/linux/threads.h
> > +++ b/include/linux/threads.h
> > @@ -34,6 +34,9 @@
> >  #define PID_MAX_LIMIT (CONFIG_BASE_SMALL ? PAGE_SIZE * 8 : \
> >       (sizeof(long) > 4 ? 4 * 1024 * 1024 : PID_MAX_DEFAULT))
> >
> > +#define CPU_ID_SHIFT 23
> > +#define CPU_ID_MASK  0xff800000
>
> This only supports 256 CPUs. I think it doesn't make sense to try to
> squish CPU and Task IDs into 32 bits.
>
> What about introducing a caller_id option to always only print the CPU
> ID? Or do you really need Task _and_ CPU?
Yes, I need it.
For SOC manufacturer, sometimes cpu is not stable, we need some debug
tools for this exceptions.
When an exception occurs, we may not be able to detect it in a timely
manner, but through Task _and_ CPU, we can roughly locate the CPU at
the time of the exception.

Thanks

Enlin

>
> John Ogness