From: Joel Brobecker <brobecker@adacore.com>
To: Alan Hayward <alan.hayward@arm.com>
Cc: gdb-patches@sourceware.org, nd@arm.com
Subject: Re: [PATCH] Aarch64 SVE: Fix stack smashing when calling functions
Date: Mon, 17 Sep 2018 18:42:00 -0000 [thread overview]
Message-ID: <20180917184205.GG19172@adacore.com> (raw)
In-Reply-To: <20180917144540.78906-1-alan.hayward@arm.com>
Hi Alan,
> Using "call" on a function that passes arguments via float registers can cause
> gdb to overflow buffers.
> Ensure enough memory is reserved to hold a full FP register.
>
> 2018-09-17 Alan Hayward <alan.hayward@arm.com>
>
> * aarch64-tdep.c (pass_in_v): Use register size.
> (aarch64_extract_return_value): Likewise.
> (aarch64_store_return_value): Likewise.
Do we have a testcase already that demonstrates the problem?
Otherwise, it would be nice to add one.
> diff --git a/gdb/aarch64-tdep.c b/gdb/aarch64-tdep.c
> index 6993e9061e..516eb138dc 100644
> --- a/gdb/aarch64-tdep.c
> +++ b/gdb/aarch64-tdep.c
> @@ -1358,7 +1358,10 @@ pass_in_v (struct gdbarch *gdbarch,
> if (info->nsrn < 8)
> {
> int regnum = AARCH64_V0_REGNUM + info->nsrn;
> - gdb_byte reg[V_REGISTER_SIZE];
> + /* Enough space for a full vector register. */
> + gdb_byte reg[register_size (gdbarch, regnum)];
> + gdb_static_assert (AARCH64_V0_REGNUM == AARCH64_SVE_Z0_REGNUM);
> + gdb_assert (len <= sizeof (reg));
Could you explain the relationship between making the buffer large
enough, which is the purpose of this patch, and the assertion that
AARCH64_V0_REGNUM == AARCH64_SVE_Z0_REGNUM?
I don't see a problem with that assertion, but for archeology
purposes, it is better to decorelate changes that are independent.
It helps better document why we introduced changes.
>
> info->argnum++;
> info->nsrn++;
> @@ -1929,7 +1932,10 @@ aarch64_extract_return_value (struct type *type, struct regcache *regs,
> for (int i = 0; i < elements; i++)
> {
> int regno = AARCH64_V0_REGNUM + i;
> - bfd_byte buf[V_REGISTER_SIZE];
> + /* Enough space for a full vector register. */
> + gdb_byte buf[register_size (gdbarch, regno)];
> + gdb_static_assert (AARCH64_V0_REGNUM == AARCH64_SVE_Z0_REGNUM);
> + gdb_assert (len <= sizeof (buf));
>
> if (aarch64_debug)
> {
> @@ -2039,7 +2045,10 @@ aarch64_store_return_value (struct type *type, struct regcache *regs,
> for (int i = 0; i < elements; i++)
> {
> int regno = AARCH64_V0_REGNUM + i;
> - bfd_byte tmpbuf[V_REGISTER_SIZE];
> + /* Enough space for a full vector register. */
> + gdb_byte tmpbuf[register_size (gdbarch, regno)];
> + gdb_static_assert (AARCH64_V0_REGNUM == AARCH64_SVE_Z0_REGNUM);
> + gdb_assert (len <= sizeof (tmpbuf));
>
> if (aarch64_debug)
> {
> --
> 2.15.2 (Apple Git-101.1)
Thank you!
--
Joel
next prev parent reply other threads:[~2018-09-17 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 14:45 Alan Hayward
2018-09-17 18:42 ` Joel Brobecker [this message]
2018-09-18 9:08 ` Alan Hayward
2018-09-18 14:40 ` Joel Brobecker
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=20180917184205.GG19172@adacore.com \
--to=brobecker@adacore.com \
--cc=alan.hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@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