public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	Bernard Metzler <bmt@zurich.ibm.com>,
	Doug Ledford <dledford@redhat.com>,
	Jason Gunthorpe <jgg@ziepe.ca>
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RDMA/siw: Fix compiler warnings on 32-bit due to u64/pointer abuse
Date: Mon, 19 Aug 2019 09:56:20 -0700	[thread overview]
Message-ID: <581e7d79ed75484beb227672b2695ff14e1f1e34.camel@perches.com> (raw)
In-Reply-To: <20190819100526.13788-1-geert@linux-m68k.org>

On Mon, 2019-08-19 at 12:05 +0200, Geert Uytterhoeven wrote:
> When compiling on 32-bit:
> 
>     drivers/infiniband/sw/siw/siw_cq.c:76:20: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
>     drivers/infiniband/sw/siw/siw_qp.c:952:28: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
[]
> Fix this by applying the following rules:
>   1. When printing a u64, the %llx format specififer should be used,
>      instead of casting to a pointer, and printing the latter.
>   2. When assigning a pointer to a u64, the pointer should be cast to
>      uintptr_t, not u64,
>   3. When casting from u64 to pointer, an intermediate cast to uintptr_t
>      should be added,

I think a cast to unsigned long is rather more common.

uintptr_t is used ~1300 times in the kernel.
I believe a cast to unsigned long is much more common.

It might be useful to add something to the Documentation
for this style.  Documentation/process/coding-style.rst

And trivia:

> > diff --git a/drivers/infiniband/sw/siw/siw_verbs.c b/drivers/infiniband/sw/siw/siw_verbs.c
[]
> @@ -842,8 +842,8 @@ int siw_post_send(struct ib_qp *base_qp, const struct ib_send_wr *wr,
>  			rv = -EINVAL;
>  			break;
>  		}
> -		siw_dbg_qp(qp, "opcode %d, flags 0x%x, wr_id 0x%p\n",
> -			   sqe->opcode, sqe->flags, (void *)sqe->id);
> +		siw_dbg_qp(qp, "opcode %d, flags 0x%x, wr_id 0x%llx\n",
> +			   sqe->opcode, sqe->flags, sqe->id);

Printing possible pointers as %llx is generally not a good idea
given the desire for %p obfuscation.



  parent reply	other threads:[~2019-08-19 16:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19 10:05 [PATCH] RDMA/siw: Fix compiler warnings on 32-bit due to u64/pointer abuse Geert Uytterhoeven
2019-08-19 12:24 ` Jason Gunthorpe
2019-08-19 13:36   ` Bernard Metzler
2019-08-19 13:52     ` Jason Gunthorpe
2019-08-19 14:15       ` Bernard Metzler
2019-08-19 14:18         ` Jason Gunthorpe
2019-08-19 14:52           ` Bernard Metzler
2019-08-19 15:07             ` Jason Gunthorpe
2019-08-19 15:54               ` Bernard Metzler
2019-08-19 16:05                 ` Jason Gunthorpe
2019-08-19 16:29                   ` Bernard Metzler
2019-08-19 16:35                     ` Jason Gunthorpe
2019-08-19 17:39                       ` Bernard Metzler
2019-08-19 18:00                         ` Jason Gunthorpe
2019-08-19 21:40                           ` Bernard Metzler
2019-08-19 22:22                             ` Jason Gunthorpe
2019-08-19 16:56 ` Joe Perches [this message]
2019-08-19 17:14   ` Geert Uytterhoeven
2019-08-19 17:26     ` Bernard Metzler
2019-08-27 14:17     ` David Laight
2019-08-27 17:29       ` Geert Uytterhoeven
2019-08-27 17:46         ` Al Viro
2019-08-27 17:59           ` Geert Uytterhoeven
2019-08-27 18:33             ` Joe Perches
2019-08-28  8:27               ` David Laight

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=581e7d79ed75484beb227672b2695ff14e1f1e34.camel@perches.com \
    --to=joe@perches.com \
    --cc=bmt@zurich.ibm.com \
    --cc=dledford@redhat.com \
    --cc=geert@linux-m68k.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    /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