Linux-HyperV List
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: sashiko-reviews@lists.linux.dev
Cc: linux-hyperv@vger.kernel.org
Subject: Re: [PATCH v3 10/10] RDMA: Replace memset with = {} pattern for ib_respond_udata()
Date: Wed, 13 May 2026 20:23:35 -0300	[thread overview]
Message-ID: <20260513232335.GE787748@nvidia.com> (raw)
In-Reply-To: <20260513205916.926F0C19425@smtp.kernel.org>

On Wed, May 13, 2026 at 08:59:15PM +0000, sashiko-bot@kernel.org wrote:
> The commit message notes that qedr_copy_qp_uresp() is already called with
> zeroed memory. If the caller is using aggregate initialization (= {}) on
> the stack, this may not completely zero the memory.

This isn't true, c23 standardized ={} as "empty initializtion"
clearing padding and the kernel has long relied on this behavior.

Jason

  reply	other threads:[~2026-05-13 23:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12  0:09 [PATCH v3 00/10] Convert all drivers to the new udata response flow Jason Gunthorpe
2026-05-12  0:09 ` [PATCH v3 01/10] RDMA: Use ib_is_udata_in_empty() for places calling ib_is_udata_cleared() Jason Gunthorpe
2026-05-12  0:09 ` [PATCH v3 02/10] IB/rdmavt: Don't abuse udata and ib_respond_udata() Jason Gunthorpe
2026-05-13  3:12   ` sashiko-bot
2026-05-13 11:38     ` Jason Gunthorpe
2026-05-13 13:45       ` Dennis Dalessandro
2026-05-12  0:09 ` [PATCH v3 03/10] RDMA: Convert drivers using min to ib_respond_udata() Jason Gunthorpe
2026-05-12  0:09 ` [PATCH v3 04/10] RDMA: Convert drivers using sizeof() " Jason Gunthorpe
2026-05-12  0:09 ` [PATCH v3 05/10] RDMA/cxgb4: Convert " Jason Gunthorpe
2026-05-12  0:09 ` [PATCH v3 06/10] RDMA/qedr: Replace qedr_ib_copy_to_udata() with ib_respond_udata() Jason Gunthorpe
2026-05-13 19:07   ` sashiko-bot
2026-05-12  0:09 ` [PATCH v3 07/10] RDMA/mlx: Replace response_len " Jason Gunthorpe
2026-05-12  0:09 ` [PATCH v3 08/10] RDMA: Use proper driver data response structs instead of open coding Jason Gunthorpe
2026-05-12  0:09 ` [PATCH v3 09/10] RDMA: Add missed = {} initialization to uresp structs Jason Gunthorpe
2026-05-12  0:09 ` [PATCH v3 10/10] RDMA: Replace memset with = {} pattern for ib_respond_udata() Jason Gunthorpe
2026-05-13 20:59   ` sashiko-bot
2026-05-13 23:23     ` Jason Gunthorpe [this message]
2026-05-14  8:22 ` [PATCH v3 00/10] Convert all drivers to the new udata response flow Leon Romanovsky

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=20260513232335.GE787748@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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