From: Ronja Meyer <rnj@google.com>
To: Jack Wang <jinpu.wang@cloud.ionos.com>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Tom Peng <tom_peng@usish.com>, Kevin Ao <aoqingyun@usish.com>,
Lindar Liu <lindar_liu@usish.com>,
James Bottomley <James.Bottomley@suse.de>
Cc: jack wang <jack_wang@usish.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Ronja Meyer <rnj@google.com>,
stable@vger.kernel.org, Igor Pylypiv <ipylypiv@google.com>
Subject: [PATCH 0/2] scsi: pm8001: Fix struct layout and FORTIFY_SOURCE crash
Date: Fri, 15 May 2026 12:15:38 +0000 [thread overview]
Message-ID: <20260515-fortify_pm80-v1-0-2863187f6d4b@google.com> (raw)
This patch series:
- Fixes a crash when the driver is built with FORTIFY_SOURCE=y.
- Aligns the struct layout of hw_event_resp to what the HBA believes
it looks like.
- Simplifies code previously required to work around the incorrect
struct definition.
Testing:
- Verified I can still read from disks using the pm80xx driver.
- I do not have pm8001 hardware available to verify against.
Signed-off-by: Ronja Meyer <rnj@google.com>
---
Ronja Meyer (2):
scsi: pm8001: Redefine sas_identify_frame structure
scsi: pm8001: Match hw_event_resp to HBA data layout
drivers/scsi/pm8001/pm8001_hwi.c | 6 +--
drivers/scsi/pm8001/pm8001_hwi.h | 103 +++++++++++++++++++++++++++++++++++++--
drivers/scsi/pm8001/pm80xx_hwi.c | 6 +--
drivers/scsi/pm8001/pm80xx_hwi.h | 4 +-
4 files changed, 108 insertions(+), 11 deletions(-)
---
base-commit: 98f69975d4c0434ca2e6e8cfa1d8d51647a20593
change-id: 20260515-fortify_pm80-b527a10c89d0
Best regards,
--
Ronja Meyer <rnj@google.com>
next reply other threads:[~2026-05-15 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 12:15 Ronja Meyer [this message]
2026-05-15 12:15 ` [PATCH 1/2] scsi: pm8001: Redefine sas_identify_frame structure Ronja Meyer
2026-05-15 14:48 ` James Bottomley
2026-05-15 12:15 ` [PATCH 2/2] scsi: pm8001: Match hw_event_resp to HBA data layout Ronja Meyer
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=20260515-fortify_pm80-v1-0-2863187f6d4b@google.com \
--to=rnj@google.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=James.Bottomley@suse.de \
--cc=aoqingyun@usish.com \
--cc=ipylypiv@google.com \
--cc=jack_wang@usish.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=lindar_liu@usish.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=stable@vger.kernel.org \
--cc=tom_peng@usish.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