Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Lancelot SIX <Lancelot.Six@amd.com>
To: Tankut Baris Aktemur <tankutbaris.aktemur@amd.com>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/amd-dbgapi-target: assert register size in fetch/store_registers
Date: Mon, 11 May 2026 13:15:08 +0100	[thread overview]
Message-ID: <d6292121-6675-40f0-883c-7cb3a81c50ed@amd.com> (raw)
In-Reply-To: <20260511115826.2891319-1-tankutbaris.aktemur@amd.com>

On 11/05/2026 12:58, Tankut Baris Aktemur wrote:
> Assert that register size is not larger than the max register size as
> a safety measure against buffer overflow.
> ---
>   gdb/amd-dbgapi-target.c | 11 +++++++----
>   1 file changed, 7 insertions(+), 4 deletions(-)
> 
> diff --git a/gdb/amd-dbgapi-target.c b/gdb/amd-dbgapi-target.c
> index b7d5ee7de9f..421ec8599ed 100644
> --- a/gdb/amd-dbgapi-target.c
> +++ b/gdb/amd-dbgapi-target.c
> @@ -1968,10 +1968,12 @@ amd_dbgapi_target::fetch_registers (struct regcache *regcache, int regno)
>     amdgpu_gdbarch_tdep *tdep = get_amdgpu_gdbarch_tdep (gdbarch);
>     amd_dbgapi_wave_id_t wave_id = get_amd_dbgapi_wave_id (regcache->ptid ());
>     gdb_byte raw[AMDGPU_MAX_REGISTER_SIZE];
> +  ULONGEST reg_size = register_type (gdbarch, regno)->length ();
> +  gdb_assert (reg_size <= AMDGPU_MAX_REGISTER_SIZE);
> +
>     amd_dbgapi_status_t status
>       = amd_dbgapi_read_register (wave_id, tdep->register_ids[regno], 0,
> -				register_type (gdbarch, regno)->length (),
> -				raw);
> +				reg_size, raw);
>   
>     if (status == AMD_DBGAPI_STATUS_SUCCESS)
>       regcache->raw_supply (regno, raw);
> @@ -1994,6 +1996,8 @@ amd_dbgapi_target::store_registers (struct regcache *regcache, int regno)
>     gdb_assert (is_amdgpu_arch (gdbarch));
>   
>     gdb_byte raw[AMDGPU_MAX_REGISTER_SIZE];
> +  ULONGEST reg_size = register_type (gdbarch, regno)->length ();
> +  gdb_assert (reg_size <= AMDGPU_MAX_REGISTER_SIZE);
>     regcache->raw_collect (regno, &raw);
>   
>     amdgpu_gdbarch_tdep *tdep = get_amdgpu_gdbarch_tdep (gdbarch);
> @@ -2018,8 +2022,7 @@ amd_dbgapi_target::store_registers (struct regcache *regcache, int regno)
>     amd_dbgapi_wave_id_t wave_id = get_amd_dbgapi_wave_id (regcache->ptid ());
>     amd_dbgapi_status_t status
>       = amd_dbgapi_write_register (wave_id, tdep->register_ids[regno], 0,
> -				 register_type (gdbarch, regno)->length (),
> -				 raw);
> +				 reg_size, raw);
>   
>     if (status != AMD_DBGAPI_STATUS_SUCCESS)
>       warning (_("Couldn't write register %s (#%d)."),

Hi Baris,

Thanks, this looks good to me, tested on gfx1031.

Approved-by: Lancelot Six <lancelot.six@amd.com>

Best,
Lancelot.

      reply	other threads:[~2026-05-11 12:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 11:58 Tankut Baris Aktemur
2026-05-11 12:15 ` Lancelot SIX [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=d6292121-6675-40f0-883c-7cb3a81c50ed@amd.com \
    --to=lancelot.six@amd.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tankutbaris.aktemur@amd.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