From: Leon Romanovsky <leon@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "Marciniszyn, Mike" <mike.marciniszyn@cornelisnetworks.com>,
Guo Zhi <qtxuning1999@sjtu.edu.cn>,
"Dalessandro, Dennis" <dennis.dalessandro@cornelisnetworks.com>,
"dledford@redhat.com" <dledford@redhat.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] infiniband hfi1: fix misuse of %x in ipoib_tx.c
Date: Thu, 23 Sep 2021 09:45:51 +0300 [thread overview]
Message-ID: <YUwin2cn8X5GGjyY@unreal> (raw)
In-Reply-To: <276b9343-c23d-ac15-bb73-d7b42e7e7f0f@acm.org>
On Wed, Sep 22, 2021 at 11:05:42AM -0700, Bart Van Assche wrote:
> On 9/22/21 10:51 AM, Marciniszyn, Mike wrote:
> > > Subject: [PATCH] infiniband hfi1: fix misuse of %x in ipoib_tx.c
> > >
> > > Pointers should be printed with %p or %px rather than cast to (unsigned long
> > > long) and printed with %llx.
> > > Change %llx to %p to print the pointer.
> > >
> > > Signed-off-by: Guo Zhi <qtxuning1999@sjtu.edu.cn>
> >
> > The unsigned long long was originally used to insure the entire accurate pointer as emitted.
> >
> > This is to ensure the pointers in prints and event traces match values in stacks and register dumps.
> >
> > I think the %p will obfuscate the pointer so %px is correct for our use case.
>
> How about applying Guo's patch and adding a configuration option to the
> kernel for disabling pointer hashing for %p and related format specifiers?
Isn't kptr_restrict sysctl is for that?
> Pointer hashing is useful on production systems but not on development
> systems.
>
> Thanks,
>
> Bart.
>
next prev parent reply other threads:[~2021-09-23 6:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 13:48 [PATCH] infiniband hfi1: fix misuse of %x in ipoib_tx.c Guo Zhi
2021-09-22 17:51 ` Marciniszyn, Mike
2021-09-22 18:05 ` Bart Van Assche
2021-09-23 6:45 ` Leon Romanovsky [this message]
2021-09-23 11:04 ` Marciniszyn, Mike
2021-09-23 11:44 ` Leon Romanovsky
2021-09-23 12:18 ` Marciniszyn, Mike
2021-09-24 2:46 ` Bart Van Assche
2021-09-24 14:43 ` Marciniszyn, Mike
2021-09-25 0:20 ` Guo Zhi
2021-09-23 11:03 ` Marciniszyn, Mike
2021-09-23 13:15 ` Jason Gunthorpe
2021-09-23 2:03 ` 郭志
2021-09-23 12:51 ` 郭志
2021-09-27 13:05 ` Marciniszyn, Mike
2021-09-27 17:42 ` Jason Gunthorpe
-- strict thread matches above, loose matches on Subject: below --
2021-09-22 12:33 Guo Zhi
2021-09-22 12:37 ` Dennis Dalessandro
2021-09-24 14:46 ` Marciniszyn, Mike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YUwin2cn8X5GGjyY@unreal \
--to=leon@kernel.org \
--cc=bvanassche@acm.org \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@cornelisnetworks.com \
--cc=qtxuning1999@sjtu.edu.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).