Re: Fix out-of-bounds in the function GetCommandTagName - Mailing list pgsql-hackers

From David Rowley
Subject Re: Fix out-of-bounds in the function GetCommandTagName
Date
Msg-id CAApHDvqhEDo77c1PTtUcHr6bL7bqUBvo7YTRJo9TamEqTEYh9A@mail.gmail.com
Whole thread Raw
In response to [MASSMAIL]Fix out-of-bounds in the function GetCommandTagName  (Ranier Vilela <ranier.vf@gmail.com>)
Responses Re: Fix out-of-bounds in the function GetCommandTagName
Re: Fix out-of-bounds in the function GetCommandTagName
List pgsql-hackers
On Mon, 15 Apr 2024 at 11:17, Ranier Vilela <ranier.vf@gmail.com> wrote:
> Coverity has reported some out-of-bounds bugs
> related to the GetCommandTagName function.
>
> The size of the array is defined by COMMAND_TAG_NEXTTAG enum,
> whose value currently corresponds to 193.
> Since enum items are evaluated starting at zero, by default.

I think the change makes sense. I don't see any good reason to define
COMMAND_TAG_NEXTTAG or force the compiler's hand when it comes to
sizing that array.

Clearly, Coverity does not understand that we'll never call any of
those GetCommandTag* functions with COMMAND_TAG_NEXTTAG.

> Patch attached.

You seem to have forgotten to attach it, but my comments above were
written with the assumption that the patch is what I've attached here.

David

Attachment

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: [MASSMAIL]Stability of queryid in minor versions
Next
From: Michael Paquier
Date:
Subject: [MASSMAIL]meson and pg_config --libs/--ldflags_ex