Re: [PATCH] bms_prev_member() can read beyond the end of the array of allocated words
От | David Rowley |
---|---|
Тема | Re: [PATCH] bms_prev_member() can read beyond the end of the array of allocated words |
Дата | |
Msg-id | CAApHDvpOwmEa46bJurnCsp-Ug8A8mnmbJt+bn9txBUg3SGbNZg@mail.gmail.com обсуждение исходный текст |
Ответ на | [PATCH] bms_prev_member() can read beyond the end of the array of allocated words (Greg Burd <greg@burd.me>) |
Ответы |
Re: [PATCH] bms_prev_member() can read beyond the end of the array of allocated words
Re: [PATCH] bms_prev_member() can read beyond the end of the array of allocated words |
Список | pgsql-hackers |
On Fri, 15 Aug 2025 at 01:21, Greg Burd <greg@burd.me> wrote: > I've been working on Bitmapset and while creating a test suite for it I > found that there is a missing bounds check in bms_prev_member(). The > function takes the prevbit argument and converts it to an index into the > words array using WORDNUM() without checking to ensure that prevbit is > within the bounds of the possible values (e.g. nwords * > BITS_PER_BITMAPWORD) in the set. This means that $subject resulting in > a confusing return value when the expected value should be the highest > bit set. There's a comment saying: * "prevbit" must NOT be more than one above the highest possible bit that can * be set at the Bitmapset at its current size. So looks like it's the fault of the calling code and not an issue with bms_prev_member(). David
В списке pgsql-hackers по дате отправления: