From: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
---|---|
To: | Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Avoid incomplete copy string (src/backend/access/transam/xlog.c) |
Date: | 2024-06-24 00:08:47 |
Message-ID: | CAFcNs+p2NSyT0Vs2gFxGwFn02jEj_DgHWK0N-F18EtENh-8TEw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, 23 Jun 2024 at 20:51 Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> wrote:
> Hi.
>
> In src/include/access/xlogbackup.h, the field *name*
> has one byte extra to store null-termination.
>
> But, in the function *do_pg_backup_start*,
> I think that is a mistake in the line (8736):
>
> memcpy(state->name, backupidstr, strlen(backupidstr));
>
> memcpy with strlen does not copy the whole string.
> strlen returns the exact length of the string, without
> the null-termination.
>
> So, I think this can result in errors,
> like in the function *build_backup_content*
> (src/backend/access/transam/xlogbackup.c)
> Where *appendStringInfo* expects a string with null-termination.
>
> appendStringInfo(result, "LABEL: %s\n", state->name);
>
> To fix, copy strlen size plus one byte, to include the null-termination.
>
>
Doesn’t “sizeof” solve the problem? It take in account the null-termination
character.
Fabrízio de Royes Mello
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2024-06-24 00:10:56 | Re: Optimize numeric.c mul_var() using the Karatsuba algorithm |
Previous Message | Ranier Vilela | 2024-06-23 23:51:26 | Avoid incomplete copy string (src/backend/access/transam/xlog.c) |