From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] SCSI fixes for 7.1-rc5+
Date: Sun, 31 May 2026 11:33:58 -0400 [thread overview]
Message-ID: <145613e24e565d8a539ee4d647d4766541fce526.camel@HansenPartnership.com> (raw)
Sorry for the late pull request, I got roped into doing stuff on Saturday.
The following changes since commit b71cb088b2e3427924a470fc43e7aedb8a40d2e3:
scsi: target: tcm_loop: Fix NULL ptr dereference (2026-05-14 22:21:01 -0400)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git tags/scsi-fixes
for you to fetch changes up to 85db7391310b1304d2dc8ae3b0b12105a9567147:
scsi: target: iscsi: Validate CHAP_R length before base64 decode (2026-05-22 23:06:00 -0400)
----------------------------------------------------------------
Two core changes, the only one of significance being the change to kick queues
in SDEV_CANCEL which had a small window for stuck requests. The major driver
fixes are the one to the FC transport class to widen the FPIN counter to
counter a theoretical (and privileged) fabric traffic injection attack and the
other is an iscsi fix where a malicious target could trick the kernel into an
output buffer overrun. Both the driver fixes were AI assisted.
----------------------------------------------------------------
Alexander Perlis (1):
scsi: devinfo: Add BLIST_NO_RSOC for Promise VTrak E310f
Alexandru Hossu (1):
scsi: target: iscsi: Validate CHAP_R length before base64 decode
David Jeffery (1):
scsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues
Ewan D. Milne (1):
scsi: scsi_debug: Add missing newline in scsi_debug_device_reset()
Michael Bommarito (4):
scsi: scsi_transport_fc: Widen FPIN pname walker counter to u32
scsi: fcoe: Reject FIP descriptors with zero fip_dlen in CVL walker
scsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd()
scsi: target: iscsi: Bound iscsi_encode_text_output() appends to rsp_buf
Milan P. Gandhi (1):
scsi: megaraid_sas: Fix NULL pointer dereference on firmware duplicate completion
drivers/scsi/fcoe/fcoe_ctlr.c | 2 +-
drivers/scsi/megaraid/megaraid_sas_fusion.c | 9 +++
drivers/scsi/scsi_debug.c | 2 +-
drivers/scsi/scsi_devinfo.c | 1 +
drivers/scsi/scsi_lib.c | 27 ++++++++-
drivers/scsi/scsi_transport_fc.c | 77 ++++++++++++++------------
drivers/target/iscsi/iscsi_target.c | 5 +-
drivers/target/iscsi/iscsi_target_auth.c | 19 ++++++-
drivers/target/iscsi/iscsi_target_nego.c | 7 ++-
drivers/target/iscsi/iscsi_target_parameters.c | 62 ++++++++++++++++-----
drivers/target/iscsi/iscsi_target_parameters.h | 2 +-
11 files changed, 155 insertions(+), 58 deletions(-)
Regards,
James
next reply other threads:[~2026-05-31 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 15:33 James Bottomley [this message]
2026-05-31 21:14 ` pr-tracker-bot
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=145613e24e565d8a539ee4d647d4766541fce526.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®