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: Adaptec OEM Raid Solutions <aacraid@microsemi.com>,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	linux-hardening@vger.kernel.org
Subject: Re: [PATCH 0/2] scsi: aacraid: struct sgmap: Replace 1-element arrays with flexible arrays
Date: Fri, 02 Aug 2024 21:40:51 -0400	[thread overview]
Message-ID: <yq134nm759g.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20240711212732.work.162-kees@kernel.org> (Kees Cook's message of "Thu, 11 Jul 2024 14:57:36 -0700")


Kees,

> This replaces some of the last remaining uses in the kernel of
> 1-element "fake" flexible arrays with modern C99 flexible arrays. Some
> refactoring is done to ease this, and binary differences are
> identified. For the on stack size changes in patch 2, the "yes, that
> is the source of the binary differences" debugging patch can be found
> here[1].

Applied to 6.12/scsi-staging, thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2024-08-03  1:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11 21:57 [PATCH 0/2] scsi: aacraid: struct sgmap: Replace 1-element arrays with flexible arrays Kees Cook
2024-07-11 21:57 ` [PATCH 1/2] scsi: aacraid: Rearrange order of struct aac_srb_unit Kees Cook
2024-07-11 21:57 ` [PATCH 2/2] scsi: aacraid: struct {user,}sgmap{,64,raw}: Replace 1-element arrays with flexible arrays Kees Cook
2024-08-03  1:40 ` Martin K. Petersen [this message]
2024-08-05 21:17 ` [PATCH 0/2] scsi: aacraid: struct sgmap: " Martin K. Petersen

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=yq134nm759g.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=aacraid@microsemi.com \
    --cc=kees@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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