[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB608326C26516C66ADC0526D8FCF6A@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Fri, 15 Sep 2023 16:31:03 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Enlin Mu <enlin.mu@...look.com>,
"pmladek@...e.com" <pmladek@...e.com>,
"rostedt@...dmis.org" <rostedt@...dmis.org>,
"john.ogness@...utronix.de" <john.ogness@...utronix.de>,
"senozhatsky@...omium.org" <senozhatsky@...omium.org>,
"keescook@...omium.org" <keescook@...omium.org>,
"gpiccoli@...lia.com" <gpiccoli@...lia.com>,
"enlin.mu@...soc.com" <enlin.mu@...soc.com>,
"enlinmu@...il.com" <enlinmu@...il.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-hardening@...r.kernel.org" <linux-hardening@...r.kernel.org>
Subject: RE: [PATCH] printk: add cpu id information to printk() output
> + return in_task() ? task_pid_nr(current) | (smp_processor_id() << CPU_ID_SHIFT) :
There are contexts and CONFIG options around pre-emption where smp_processor_id()
will throw a warning. Use raw_smp_processor_id().
-Tony
Powered by blists - more mailing lists