From: Philipp Tomsich <philipp.tomsich@vrull.eu>
To: Philipp Tomsich <philipp.tomsich@vrull.eu>,
gcc-patches@gcc.gnu.org,
Tamar Christina <tamar.christina@arm.com>,
Christoph Muellner <christoph.muellner@vrull.eu>,
richard.sandiford@arm.com
Subject: Re: [PATCH v2] aarch64: fix off-by-one in reading cpuinfo
Date: Thu, 6 Oct 2022 12:37:29 +0200 [thread overview]
Message-ID: <CAAeLtUD=FD3Zu7KugRcG4Odt6E1FF-LYn29jaG_eS-wsmwJC8g@mail.gmail.com> (raw)
In-Reply-To: <mptv8oxi7w8.fsf@arm.com>
[-- Attachment #1: Type: text/plain, Size: 3906 bytes --]
On Thu, 6 Oct 2022 at 12:06, Richard Sandiford <richard.sandiford@arm.com>
wrote:
> Philipp Tomsich <philipp.tomsich@vrull.eu> writes:
> > Fixes: 341573406b39
> >
> > Don't subtract one from the result of strnlen() when trying to point
> > to the first character after the current string. This issue would
> > cause individual characters (where the 128 byte buffers are stitched
> > together) to be lost.
> >
> > gcc/ChangeLog:
> >
> > * config/aarch64/driver-aarch64.cc (readline): Fix off-by-one.
> >
> > gcc/testsuite/ChangeLog:
> >
> > * gcc.target/aarch64/cpunative/info_18: New test.
> > * gcc.target/aarch64/cpunative/native_cpu_18.c: New test.
> >
> > Signed-off-by: Philipp Tomsich <philipp.tomsich@vrull.eu>
> >
> > ---
> >
> > Changes in v2:
> > - Add a a regression test (as per review comment).
> >
> > gcc/config/aarch64/driver-aarch64.cc | 4 ++--
> > .../gcc.target/aarch64/cpunative/info_18 | 8 ++++++++
> > .../gcc.target/aarch64/cpunative/native_cpu_18.c | 15 +++++++++++++++
> > 3 files changed, 25 insertions(+), 2 deletions(-)
> > create mode 100644 gcc/testsuite/gcc.target/aarch64/cpunative/info_18
> > create mode 100644
> gcc/testsuite/gcc.target/aarch64/cpunative/native_cpu_18.c
> >
> > diff --git a/gcc/config/aarch64/driver-aarch64.cc
> b/gcc/config/aarch64/driver-aarch64.cc
> > index 52ff537908e..48250e68034 100644
> > --- a/gcc/config/aarch64/driver-aarch64.cc
> > +++ b/gcc/config/aarch64/driver-aarch64.cc
> > @@ -203,9 +203,9 @@ readline (FILE *f)
> > return std::string ();
> > /* If we're not at the end of the line then override the
> > \0 added by fgets. */
> > - last = strnlen (buf, size) - 1;
> > + last = strnlen (buf, size);
> > }
> > - while (!feof (f) && buf[last] != '\n');
> > + while (!feof (f) && (last > 0 && buf[last - 1] != '\n'));
>
> Very minor, but: I think the normal GCC style would be to avoid the
> extra (...).
>
> OK with that change, thanks. OK for backports too after a settling period.
>
Applied to master (with that change). Thanks!
I'll backport around the end of this month, if no new issues are caused by
this change.
Philipp.
>
> Richard
>
> >
> > std::string result (buf);
> > free (buf);
> > diff --git a/gcc/testsuite/gcc.target/aarch64/cpunative/info_18
> b/gcc/testsuite/gcc.target/aarch64/cpunative/info_18
> > new file mode 100644
> > index 00000000000..25061a4abe8
> > --- /dev/null
> > +++ b/gcc/testsuite/gcc.target/aarch64/cpunative/info_18
> > @@ -0,0 +1,8 @@
> > +processor : 0
> > +BogoMIPS : 2000.00
> > +Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp
> asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 asimddp sha512 asimdfhm
> dit uscat ilrcpc flagm ssbs sb dcpodp flagm2 frint i8mm bf16 rng ecv
> > +CPU implementer : 0xc0
> > +CPU architecture: 8
> > +CPU variant : 0x0
> > +CPU part : 0xac3
> > +CPU revision : 0
> > diff --git a/gcc/testsuite/gcc.target/aarch64/cpunative/native_cpu_18.c
> b/gcc/testsuite/gcc.target/aarch64/cpunative/native_cpu_18.c
> > new file mode 100644
> > index 00000000000..b5f0a3005f5
> > --- /dev/null
> > +++ b/gcc/testsuite/gcc.target/aarch64/cpunative/native_cpu_18.c
> > @@ -0,0 +1,15 @@
> > +/* { dg-do compile { target { { aarch64*-*-linux*} && native } } } */
> > +/* { dg-set-compiler-env-var GCC_CPUINFO
> "$srcdir/gcc.target/aarch64/cpunative/info_18" } */
> > +/* { dg-additional-options "-mcpu=native" } */
> > +
> > +int main()
> > +{
> > + return 0;
> > +}
> > +
> > +/* { dg-final { scan-assembler {\.arch
> armv8.6-a\+crc\+fp16\+aes\+sha3\+rng} } } */
> > +
> > +/* Test one where the boundary of buffer size would overwrite the last
> > + character read when stitching the fgets-calls together. With the
> > + test data provided, this would truncate the 'sha512' into 'ha512'
> > + (dropping the 'sha3' feature). */
>
prev parent reply other threads:[~2022-10-06 10:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 9:28 Philipp Tomsich
2022-10-06 10:05 ` Richard Sandiford
2022-10-06 10:37 ` Philipp Tomsich [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='CAAeLtUD=FD3Zu7KugRcG4Odt6E1FF-LYn29jaG_eS-wsmwJC8g@mail.gmail.com' \
--to=philipp.tomsich@vrull.eu \
--cc=christoph.muellner@vrull.eu \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@arm.com \
--cc=tamar.christina@arm.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 read-only IMAP folder(s) and NNTP newsgroup(s).