From: sashiko-bot@kernel.org
To: "Yehyeong Lee" <yhlee@isslab.korea.ac.kr>
Cc: linux-s390@vger.kernel.org, "Heiko Carstens" <hca@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>
Subject: Re: [PATCH] scsi: zfcp: bound the RSCN page walk to the status read payload
Date: Fri, 23 Oct 2026 02:25:07 +0000 [thread overview]
Message-ID: <sashiko-outbox-182230@kernel.org> (raw)
In-Reply-To: <20261023022056.3106651-1-yhlee@isslab.korea.ac.kr>
> zfcp_fc_incoming_rscn() takes the number of RSCN pages from rscn_plen in
> the received ELS and walks that many four byte pages out of the status
> read buffer payload. The fabric chooses rscn_plen, it is a 16 bit field,
> and nothing compares it against the payload. A value of 65535 gives 16383
> entries, so the loop reads up to 65532 bytes out of a payload of
> FSF_STATUS_READ_PAYLOAD_SIZE, which is 4032. The status read buffer is a
> single page and its payload ends at the page boundary, so the walk
> continues into whatever follows that page.
>
> Every iteration also hands the four bytes it just read to
> zfcp_fc_enqueue_event(), and that event reaches user space through
> fc_host_post_event(), so the bytes past the payload are reported and not
> merely read.
>
> libfc bounds the same field. fc_disc_recv_rscn_req() refuses an RSCN whose
> [ ... ]
> payload size.
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Cc: stable@vger.kernel.org
> Signed-off-by: Yehyeong Lee <yhlee@isslab.korea.ac.kr>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261023022056.3106651-1-yhlee@isslab.korea.ac.kr?part=1
prev parent reply other threads:[~2026-10-23 2:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 2:20 [PATCH] scsi: zfcp: bound the RSCN page walk to the status read payload Yehyeong Lee
2026-10-23 2:25 ` sashiko-bot [this message]
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=sashiko-outbox-182230@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=yhlee@isslab.korea.ac.kr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.