From: Nick Desaulniers <ndesaulniers@google.com>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: dledford@redhat.com, jgg@ziepe.ca, linux-rdma@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] IB/mlx4: Avoid implicit enumerated type conversion
Date: Mon, 24 Sep 2018 15:24:36 -0700 [thread overview]
Message-ID: <CAKwvOdkr+ovYgmqWENHkCcAWMC+xC6NYne6SBycq_KXscpHxEQ@mail.gmail.com> (raw)
In-Reply-To: <20180924195716.30848-1-natechancellor@gmail.com>
On Mon, Sep 24, 2018 at 12:57 PM Nathan Chancellor
<natechancellor@gmail.com> wrote:
>
> Clang warns when one enumerated type is implicitly converted to another.
>
> drivers/infiniband/hw/mlx4/mad.c:1811:41: warning: implicit conversion
> from enumeration type 'enum mlx4_ib_qp_flags' to different enumeration
> type 'enum ib_qp_create_flags' [-Wenum-conversion]
> qp_init_attr.init_attr.create_flags = MLX4_IB_SRIOV_TUNNEL_QP;
> ~ ^~~~~~~~~~~~~~~~~~~~~~~
>
> drivers/infiniband/hw/mlx4/mad.c:1819:41: warning: implicit conversion
> from enumeration type 'enum mlx4_ib_qp_flags' to different enumeration
> type 'enum ib_qp_create_flags' [-Wenum-conversion]
> qp_init_attr.init_attr.create_flags = MLX4_IB_SRIOV_SQP;
> ~ ^~~~~~~~~~~~~~~~~
>
> The type mlx4_ib_qp_flags explicitly provides supplemental values to the
> type ib_qp_create_flags. Make that clear to Clang by changing the
> create_flags type to u32.
>
> Reported-by: Nick Desaulniers <ndesaulniers@google.com>
> Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
> ---
> include/rdma/ib_verbs.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/rdma/ib_verbs.h b/include/rdma/ib_verbs.h
> index e463d3007a35..f6f4d9e3c8ed 100644
> --- a/include/rdma/ib_verbs.h
> +++ b/include/rdma/ib_verbs.h
> @@ -1149,7 +1149,7 @@ struct ib_qp_init_attr {
> struct ib_qp_cap cap;
> enum ib_sig_type sq_sig_type;
> enum ib_qp_type qp_type;
> - enum ib_qp_create_flags create_flags;
> + u32 create_flags;
I think it might be better to just have explicit casts at the
assignment. What do the maintainers think?
>
> /*
> * Only needed for special QP types, or when using the RW API.
> --
> 2.19.0
>
--
Thanks,
~Nick Desaulniers
next prev parent reply other threads:[~2018-09-24 22:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 19:57 [PATCH] IB/mlx4: Avoid implicit enumerated type conversion Nathan Chancellor
2018-09-24 22:24 ` Nick Desaulniers [this message]
2018-09-24 22:27 ` Nathan Chancellor
2018-09-24 22:29 ` Nick Desaulniers
2018-09-25 2:37 ` Jason Gunthorpe
2018-09-27 1:08 ` Nathan Chancellor
2018-09-27 4:48 ` Jason Gunthorpe
2018-09-27 20:13 ` Nick Desaulniers
2018-09-27 20:28 ` Nathan Chancellor
2018-09-27 20:34 ` Nick Desaulniers
2018-09-27 20:36 ` Nathan Chancellor
2018-09-27 22:28 ` Jason Gunthorpe
2018-09-27 22:33 ` Bart Van Assche
2018-09-27 22:42 ` Nick Desaulniers
2018-09-27 22:58 ` Jason Gunthorpe
2018-09-27 23:08 ` Bart Van Assche
2018-09-28 0:55 ` Nick Desaulniers
2018-09-28 3:04 ` Jason Gunthorpe
2018-09-27 20:43 ` [PATCH v2] " Nathan Chancellor
2018-09-27 20:53 ` Nick Desaulniers
2018-10-03 22:35 ` [PATCH] " Jason Gunthorpe
2018-10-03 22:53 ` Nick Desaulniers
2018-10-03 23:01 ` Jason Gunthorpe
2018-10-03 23:09 ` Nick Desaulniers
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=CAKwvOdkr+ovYgmqWENHkCcAWMC+xC6NYne6SBycq_KXscpHxEQ@mail.gmail.com \
--to=ndesaulniers@google.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=natechancellor@gmail.com \
/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).