From: Kees Cook <kees@kernel.org>
To: Adaptec OEM Raid Solutions <aacraid@microsemi.com>
Cc: Kees Cook <kees@kernel.org>,
"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: [PATCH 0/2] scsi: aacraid: struct sgmap: Replace 1-element arrays with flexible arrays
Date: Thu, 11 Jul 2024 14:57:36 -0700 [thread overview]
Message-ID: <20240711212732.work.162-kees@kernel.org> (raw)
Hi,
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].
Thanks!
-Kees
[1] https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=dev/v6.10-rc2/1-element&id=45e6226bcbc5e982541754eca7ac29f403e82f5e
Kees Cook (2):
scsi: aacraid: Rearrange order of struct aac_srb_unit
scsi: aacraid: struct {user,}sgmap{,64,raw}: Replace 1-element arrays
with flexible arrays
drivers/scsi/aacraid/aachba.c | 26 ++++++++++++--------------
drivers/scsi/aacraid/aacraid.h | 17 ++++++-----------
drivers/scsi/aacraid/commctrl.c | 4 ++--
drivers/scsi/aacraid/comminit.c | 3 +--
drivers/scsi/aacraid/commsup.c | 5 +++--
5 files changed, 24 insertions(+), 31 deletions(-)
--
2.34.1
next reply other threads:[~2024-07-11 21:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 21:57 Kees Cook [this message]
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 ` [PATCH 0/2] scsi: aacraid: struct sgmap: " Martin K. Petersen
2024-08-05 21:17 ` 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=20240711212732.work.162-kees@kernel.org \
--to=kees@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=aacraid@microsemi.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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