[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CH0PR01MB71533CD295D5799DC26CF857F2A49@CH0PR01MB7153.prod.exchangelabs.com>
Date: Fri, 24 Sep 2021 14:43:01 +0000
From: "Marciniszyn, Mike" <mike.marciniszyn@...nelisnetworks.com>
To: Bart Van Assche <bvanassche@....org>
CC: Guo Zhi <qtxuning1999@...u.edu.cn>,
"Dalessandro, Dennis" <dennis.dalessandro@...nelisnetworks.com>,
"dledford@...hat.com" <dledford@...hat.com>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Leon Romanovsky <leon@...nel.org>,
Jason Gunthorpe <jgg@...dia.com>
Subject: RE: [PATCH] infiniband hfi1: fix misuse of %x in ipoib_tx.c
>
> On 9/22/21 23:45, Leon Romanovsky wrote:
> > Isn't kptr_restrict sysctl is for that?
>
> Hi Leon,
>
> After I sent my email I discovered the following commit: 5ead723a20e0
> ("lib/vsprintf: no_hash_pointers prints all addresses as unhashed"; v5.12).
> I think that commit does what we need?
>
Thanks Bart,
I agree.
Jason, as to traces, I suspect we need to do the same %p thing there for existing code and any new work.
For situations for debugging in the wild, a command line arg can show the actual value. I'm ok with that.
Mike
Powered by blists - more mailing lists