public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Kees Cook <kees@kernel.org>
Cc: Saurav Kashyap <skashyap@marvell.com>,
	Javed Hasan <jhasan@marvell.com>,
	GR-QLogic-Storage-Upstream@marvell.com,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org, WangYuli <wangyuli@uniontech.com>,
	Mark Brown <broonie@kernel.org>,
	"Dr. David Alan Gilbert" <linux@treblig.org>,
	linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] scsi: qedf: Use designated initializer for struct qed_fcoe_cb_ops
Date: Mon, 05 May 2025 22:18:41 -0400	[thread overview]
Message-ID: <yq1v7qev5w0.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20250502224156.work.617-kees@kernel.org> (Kees Cook's message of "Fri, 2 May 2025 15:41:57 -0700")


Kees,

> Recent fixes to the randstruct GCC plugin allowed it to notice that
> this structure is entirely function pointers and is therefore subject
> to randomization, but doing so requires that it always use designated
> initializers. Explicitly specify the "common" member as being
> initialized.

Applied to 6.16/scsi-staging, thanks!

-- 
Martin K. Petersen

  reply	other threads:[~2025-05-06  2:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-02 22:41 [PATCH] scsi: qedf: Use designated initializer for struct qed_fcoe_cb_ops Kees Cook
2025-05-06  2:18 ` Martin K. Petersen [this message]
2025-05-07 20:22 ` Nathan Chancellor

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=yq1v7qev5w0.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=GR-QLogic-Storage-Upstream@marvell.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=broonie@kernel.org \
    --cc=jhasan@marvell.com \
    --cc=kees@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux@treblig.org \
    --cc=skashyap@marvell.com \
    --cc=wangyuli@uniontech.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