From: Cornelia Huck <cohuck@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: Collin Walling <walling@linux.ibm.com>,
david@redhat.com, mst@redhat.com, qemu-devel@nongnu.org,
pasic@linux.ibm.com, borntraeger@de.ibm.com,
qemu-s390x@nongnu.org, svens@linux.ibm.com, thuth@redhat.com,
pbonzini@redhat.com, mihajlov@linux.ibm.com, rth@twiddle.net
Subject: Re: [PATCH v3 3/8] s390/sclp: rework sclp boundary and length checks
Date: Mon, 22 Jun 2020 12:43:09 +0200 [thread overview]
Message-ID: <20200622124309.62c5bfb3.cohuck@redhat.com> (raw)
In-Reply-To: <afb07359-bfaf-90ee-f68b-9b31e6a7445e@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1669 bytes --]
On Fri, 19 Jun 2020 12:50:11 +0200
Janosch Frank <frankja@linux.ibm.com> wrote:
> On 6/19/20 12:22 AM, Collin Walling wrote:
> > Rework the SCLP boundary check to account for different SCLP commands
> > (eventually) allowing different boundary sizes.
> >
> > Move the length check code into a separate function, and introduce a
> > new function to determine the length of the read SCP data (i.e. the size
> > from the start of the struct to where the CPU entries should begin).
> >
> > The format of read CPU info is unlikely to change in the future,
> > so we do not require a separate function to calculate its length.
> >
> > Signed-off-by: Collin Walling <walling@linux.ibm.com>
>
> Acked-by: Janosch Frank <frankja@linux.ibm.com>
>
> > ---
> [...]
> > +/*
> > + * The data length denotes the start of the struct to where the first
> > + * CPU entry is to be allocated. This value also denotes the offset_cpu
> > + * field.
> > + */
> > +static inline int get_read_scp_info_data_len(void)
> > +{
> > + return offsetof(ReadInfo, entries);
> > +}
> > +
> > /* Provide information about the configuration, CPUs and storage */
> > static void read_SCP_info(SCLPDevice *sclp, SCCB *sccb)
> > {
> > @@ -74,17 +112,16 @@ static void read_SCP_info(SCLPDevice *sclp, SCCB *sccb)
> > int cpu_count;
> > int rnsize, rnmax;
> > IplParameterBlock *ipib = s390_ipl_get_iplb();
> > + int data_len = get_read_scp_info_data_len();
>
> Does somebody have a better name than data_len at hand?
I could not come up with anything better, either :(
(...)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-06-22 11:00 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 22:22 [PATCH v3 0/8] s390: Extended-Length SCCB & DIAGNOSE 0x318 Collin Walling
2020-06-18 22:22 ` [PATCH v3 1/8] s390/sclp: get machine once during read scp/cpu info Collin Walling
2020-06-19 8:12 ` Janosch Frank
2020-06-22 10:30 ` Cornelia Huck
2020-06-18 22:22 ` [PATCH v3 2/8] s390/sclp: check sccb len before filling in data Collin Walling
2020-06-19 14:45 ` David Hildenbrand
2020-06-22 10:32 ` Cornelia Huck
2020-06-24 12:01 ` Thomas Huth
2020-06-18 22:22 ` [PATCH v3 3/8] s390/sclp: rework sclp boundary and length checks Collin Walling
2020-06-19 10:50 ` Janosch Frank
2020-06-22 10:43 ` Cornelia Huck [this message]
2020-06-22 15:20 ` Christian Borntraeger
2020-06-22 15:22 ` Christian Borntraeger
2020-06-22 15:54 ` Collin Walling
2020-06-18 22:22 ` [PATCH v3 4/8] s390/sclp: read sccb from mem based on sccb length Collin Walling
2020-06-19 8:18 ` Janosch Frank
2020-06-22 10:45 ` Cornelia Huck
2020-06-18 22:22 ` [PATCH v3 5/8] s390/sclp: use cpu offset to locate cpu entries Collin Walling
2020-06-19 8:21 ` Janosch Frank
2020-06-22 10:47 ` Cornelia Huck
2020-06-18 22:22 ` [PATCH v3 6/8] s390/sclp: add extended-length sccb support for kvm guest Collin Walling
2020-06-24 12:36 ` Cornelia Huck
2020-06-24 12:40 ` Thomas Huth
2020-06-24 12:55 ` Cornelia Huck
2020-06-24 14:49 ` Collin Walling
2020-06-24 14:57 ` Cornelia Huck
2020-06-24 15:19 ` Thomas Huth
2020-06-18 22:22 ` [PATCH v3 7/8] s390/kvm: header sync for diag318 Collin Walling
2020-06-18 22:22 ` [PATCH v3 8/8] s390: guest support for diagnose 0x318 Collin Walling
2020-06-19 9:21 ` Janosch Frank
2020-06-24 12:49 ` Cornelia Huck
2020-06-18 22:33 ` [PATCH v3 0/8] s390: Extended-Length SCCB & DIAGNOSE 0x318 no-reply
2020-06-18 22:51 ` no-reply
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=20200622124309.62c5bfb3.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=mihajlov@linux.ibm.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=svens@linux.ibm.com \
--cc=thuth@redhat.com \
--cc=walling@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).