From: Yuval Shaia <yuval.shaia@oracle.com>
To: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
Cc: qemu-devel@nongnu.org, qemu-stable@nongnu.org, cohuck@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/3] hw/rdma: modify struct initialization
Date: Sun, 13 Jan 2019 21:24:40 +0200 [thread overview]
Message-ID: <20190113192439.GB10017@lap1> (raw)
In-Reply-To: <20190112150225.20294-3-marcel.apfelbaum@gmail.com>
On Sat, Jan 12, 2019 at 05:02:24PM +0200, Marcel Apfelbaum wrote:
> Do not initialize structs with {0} since some
> CLANG versions do not support it.
>
> Use memset instead.
It is easier than patching CLANG ha? :)
>
> Signed-off-by: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
> ---
> contrib/rdmacm-mux/main.c | 12 +++++++++---
> hw/rdma/rdma_backend.c | 16 ++++++++++++----
> 2 files changed, 21 insertions(+), 7 deletions(-)
>
> diff --git a/contrib/rdmacm-mux/main.c b/contrib/rdmacm-mux/main.c
> index 64676030c5..d01dc76927 100644
> --- a/contrib/rdmacm-mux/main.c
> +++ b/contrib/rdmacm-mux/main.c
> @@ -350,9 +350,11 @@ static int get_fd(const char *mad, int *fd, __be64 *gid_ifid)
> static void *umad_recv_thread_func(void *args)
> {
> int rc;
> - RdmaCmMuxMsg msg = {0};
> + RdmaCmMuxMsg msg;
> int fd = -2;
>
> + memset(&msg, 0, sizeof(msg));
> +
> msg.hdr.msg_type = RDMACM_MUX_MSG_TYPE_REQ;
> msg.hdr.op_code = RDMACM_MUX_OP_CODE_MAD;
>
> @@ -387,11 +389,13 @@ static void *umad_recv_thread_func(void *args)
> static int read_and_process(int fd)
> {
> int rc;
> - RdmaCmMuxMsg msg = {0};
> + RdmaCmMuxMsg msg;
> struct umad_hdr *hdr;
> uint32_t *comm_id = 0;
> uint16_t attr_id;
>
> + memset(&msg, 0, sizeof(msg));
> +
> rc = recv(fd, &msg, sizeof(msg), 0);
> syslog(LOG_DEBUG, "Socket %d, recv %d\n", fd, rc);
>
> @@ -744,7 +748,9 @@ static void signal_handler(int sig, siginfo_t *siginfo, void *context)
> static int init(void)
> {
> int rc;
> - struct sigaction sig = {0};
> + struct sigaction sig;
> +
> + memset(&sig, 0, sizeof(sig));
>
> rc = init_listener();
> if (rc) {
> diff --git a/hw/rdma/rdma_backend.c b/hw/rdma/rdma_backend.c
> index c28bfbd44d..92e95aa640 100644
> --- a/hw/rdma/rdma_backend.c
> +++ b/hw/rdma/rdma_backend.c
> @@ -190,9 +190,11 @@ static inline int rdmacm_mux_can_process_async(RdmaBackendDev *backend_dev)
>
> static int check_mux_op_status(CharBackend *mad_chr_be)
> {
> - RdmaCmMuxMsg msg = {0};
> + RdmaCmMuxMsg msg;
> int ret;
>
> + memset(&msg, 0, sizeof(msg));
> +
> pr_dbg("Reading response\n");
> ret = qemu_chr_fe_read_all(mad_chr_be, (uint8_t *)&msg, sizeof(msg));
> if (ret != sizeof(msg)) {
> @@ -387,10 +389,12 @@ static int build_host_sge_array(RdmaDeviceResources *rdma_dev_res,
> static int mad_send(RdmaBackendDev *backend_dev, uint8_t sgid_idx,
> union ibv_gid *sgid, struct ibv_sge *sge, uint32_t num_sge)
> {
> - RdmaCmMuxMsg msg = {0};
> + RdmaCmMuxMsg msg;
> char *hdr, *data;
> int ret;
>
> + memset(&msg, 0, sizeof(msg));
> +
> pr_dbg("num_sge=%d\n", num_sge);
>
> if (num_sge != 2) {
> @@ -1112,9 +1116,11 @@ int rdma_backend_get_gid_index(RdmaBackendDev *backend_dev,
> int rdma_backend_add_gid(RdmaBackendDev *backend_dev, const char *ifname,
> union ibv_gid *gid)
> {
> - RdmaCmMuxMsg msg = {0};
> + RdmaCmMuxMsg msg;
> int ret;
>
> + memset(&msg, 0, sizeof(msg));
> +
> pr_dbg("0x%llx, 0x%llx\n",
> (long long unsigned int)be64_to_cpu(gid->global.subnet_prefix),
> (long long unsigned int)be64_to_cpu(gid->global.interface_id));
> @@ -1138,9 +1144,11 @@ int rdma_backend_add_gid(RdmaBackendDev *backend_dev, const char *ifname,
> int rdma_backend_del_gid(RdmaBackendDev *backend_dev, const char *ifname,
> union ibv_gid *gid)
> {
> - RdmaCmMuxMsg msg = {0};
> + RdmaCmMuxMsg msg;
> int ret;
>
> + memset(&msg, 0, sizeof(msg));
> +
> pr_dbg("0x%llx, 0x%llx\n",
> (long long unsigned int)be64_to_cpu(gid->global.subnet_prefix),
> (long long unsigned int)be64_to_cpu(gid->global.interface_id));
Reviewed-by: Yuval Shaia <yuval.shaia@oracle.com>
One comment though, should subject prefixed with hw/rdma or
contrib/rdmacm-mux?
> --
> 2.17.1
>
next prev parent reply other threads:[~2019-01-13 19:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 15:02 [Qemu-devel] [PATCH 0/3] contrib/rdmacm-mux: fix clang compilation Marcel Apfelbaum
2019-01-12 15:02 ` [Qemu-devel] [PATCH 1/3] contrib/rdmacm-mux: remove Wno-format-truncation flag Marcel Apfelbaum
2019-01-13 20:32 ` Yuval Shaia
2019-01-12 15:02 ` [Qemu-devel] [PATCH 2/3] hw/rdma: modify struct initialization Marcel Apfelbaum
2019-01-13 19:24 ` Yuval Shaia [this message]
2019-01-13 19:36 ` Yuval Shaia
2019-01-14 21:23 ` Marcel Apfelbaum
2019-01-14 11:47 ` Cornelia Huck
2019-01-14 21:22 ` Marcel Apfelbaum
2019-01-12 15:02 ` [Qemu-devel] [PATCH 3/3] contrib/rdmacm-mux: fix clang compilation Marcel Apfelbaum
2019-01-13 19:26 ` Yuval Shaia
2019-01-14 11:42 ` [Qemu-devel] [PATCH 0/3] " Cornelia Huck
2019-01-14 21:26 ` Marcel Apfelbaum
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=20190113192439.GB10017@lap1 \
--to=yuval.shaia@oracle.com \
--cc=cohuck@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.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;
as well as URLs for NNTP newsgroup(s).