pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
pgsql: Fix integer-overflow problem in intarray's g_int_decompress().
6+ messages / 1 participants
[nested] [flat]

* pgsql: Fix integer-overflow problem in intarray's g_int_decompress().
@ 2024-01-07 20:20 Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 6+ messages in thread

From: Tom Lane @ 2024-01-07 20:20 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Fix integer-overflow problem in intarray's g_int_decompress().

An array element equal to INT_MAX gave this code indigestion,
causing an infinite loop that surely ended in SIGSEGV.  We fixed
some nearby problems awhile ago (cf 757c5182f) but missed this.

Report and diagnosis by Alexander Lakhin (bug #18273); patch by me

Discussion: https://postgr.es/m/18273-9a832d1da122600c@postgresql.org

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/9034a2d5123498104ef1e515c0b56d70d98d0ce2

Modified Files
--------------
contrib/intarray/_int_gist.c         | 10 ++++++----
contrib/intarray/data/test__int.data |  1 +
contrib/intarray/expected/_int.out   | 33 +++++++++++++++++----------------
contrib/intarray/sql/_int.sql        |  5 +++--
4 files changed, 27 insertions(+), 22 deletions(-)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* pgsql: Fix integer-overflow problem in intarray's g_int_decompress().
@ 2024-01-07 20:20 Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 6+ messages in thread

From: Tom Lane @ 2024-01-07 20:20 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Fix integer-overflow problem in intarray's g_int_decompress().

An array element equal to INT_MAX gave this code indigestion,
causing an infinite loop that surely ended in SIGSEGV.  We fixed
some nearby problems awhile ago (cf 757c5182f) but missed this.

Report and diagnosis by Alexander Lakhin (bug #18273); patch by me

Discussion: https://postgr.es/m/18273-9a832d1da122600c@postgresql.org

Branch
------
REL_16_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/cf6f802bf538ab1c9c0ef60a6e9d6fafdfb06b98

Modified Files
--------------
contrib/intarray/_int_gist.c         | 10 ++++++----
contrib/intarray/data/test__int.data |  1 +
contrib/intarray/expected/_int.out   | 33 +++++++++++++++++----------------
contrib/intarray/sql/_int.sql        |  5 +++--
4 files changed, 27 insertions(+), 22 deletions(-)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* pgsql: Fix integer-overflow problem in intarray's g_int_decompress().
@ 2024-01-07 20:20 Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 6+ messages in thread

From: Tom Lane @ 2024-01-07 20:20 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Fix integer-overflow problem in intarray's g_int_decompress().

An array element equal to INT_MAX gave this code indigestion,
causing an infinite loop that surely ended in SIGSEGV.  We fixed
some nearby problems awhile ago (cf 757c5182f) but missed this.

Report and diagnosis by Alexander Lakhin (bug #18273); patch by me

Discussion: https://postgr.es/m/18273-9a832d1da122600c@postgresql.org

Branch
------
REL_15_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/940ab02b53eb3a3babc9dd4dea261f5a6d8aa334

Modified Files
--------------
contrib/intarray/_int_gist.c         | 10 ++++++----
contrib/intarray/data/test__int.data |  1 +
contrib/intarray/expected/_int.out   | 33 +++++++++++++++++----------------
contrib/intarray/sql/_int.sql        |  5 +++--
4 files changed, 27 insertions(+), 22 deletions(-)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* pgsql: Fix integer-overflow problem in intarray's g_int_decompress().
@ 2024-01-07 20:20 Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 6+ messages in thread

From: Tom Lane @ 2024-01-07 20:20 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Fix integer-overflow problem in intarray's g_int_decompress().

An array element equal to INT_MAX gave this code indigestion,
causing an infinite loop that surely ended in SIGSEGV.  We fixed
some nearby problems awhile ago (cf 757c5182f) but missed this.

Report and diagnosis by Alexander Lakhin (bug #18273); patch by me

Discussion: https://postgr.es/m/18273-9a832d1da122600c@postgresql.org

Branch
------
REL_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/90e8b86fc52a4be21aec16abfb5dccfb819cc53e

Modified Files
--------------
contrib/intarray/_int_gist.c         | 10 ++++++----
contrib/intarray/data/test__int.data |  1 +
contrib/intarray/expected/_int.out   | 33 +++++++++++++++++----------------
contrib/intarray/sql/_int.sql        |  5 +++--
4 files changed, 27 insertions(+), 22 deletions(-)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* pgsql: Fix integer-overflow problem in intarray's g_int_decompress().
@ 2024-01-07 20:20 Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 6+ messages in thread

From: Tom Lane @ 2024-01-07 20:20 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Fix integer-overflow problem in intarray's g_int_decompress().

An array element equal to INT_MAX gave this code indigestion,
causing an infinite loop that surely ended in SIGSEGV.  We fixed
some nearby problems awhile ago (cf 757c5182f) but missed this.

Report and diagnosis by Alexander Lakhin (bug #18273); patch by me

Discussion: https://postgr.es/m/18273-9a832d1da122600c@postgresql.org

Branch
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/9e7432fafc9290792baa7fd4aff03387973b139b

Modified Files
--------------
contrib/intarray/_int_gist.c         | 10 ++++++----
contrib/intarray/data/test__int.data |  1 +
contrib/intarray/expected/_int.out   | 33 +++++++++++++++++----------------
contrib/intarray/sql/_int.sql        |  5 +++--
4 files changed, 27 insertions(+), 22 deletions(-)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* pgsql: Fix integer-overflow problem in intarray's g_int_decompress().
@ 2024-01-07 20:20 Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 6+ messages in thread

From: Tom Lane @ 2024-01-07 20:20 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

Fix integer-overflow problem in intarray's g_int_decompress().

An array element equal to INT_MAX gave this code indigestion,
causing an infinite loop that surely ended in SIGSEGV.  We fixed
some nearby problems awhile ago (cf 757c5182f) but missed this.

Report and diagnosis by Alexander Lakhin (bug #18273); patch by me

Discussion: https://postgr.es/m/18273-9a832d1da122600c@postgresql.org

Branch
------
REL_12_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/1c7443521f856dfb5f6731ff6fc0865a67a29f14

Modified Files
--------------
contrib/intarray/_int_gist.c         | 10 ++++++----
contrib/intarray/data/test__int.data |  1 +
contrib/intarray/expected/_int.out   | 16 ++++++++--------
3 files changed, 15 insertions(+), 12 deletions(-)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread


end of thread, other threads:[~2024-01-07 20:20 UTC | newest]

Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-01-07 20:20 pgsql: Fix integer-overflow problem in intarray's g_int_decompress(). Tom Lane <tgl@sss.pgh.pa.us>
2024-01-07 20:20 pgsql: Fix integer-overflow problem in intarray's g_int_decompress(). Tom Lane <tgl@sss.pgh.pa.us>
2024-01-07 20:20 pgsql: Fix integer-overflow problem in intarray's g_int_decompress(). Tom Lane <tgl@sss.pgh.pa.us>
2024-01-07 20:20 pgsql: Fix integer-overflow problem in intarray's g_int_decompress(). Tom Lane <tgl@sss.pgh.pa.us>
2024-01-07 20:20 pgsql: Fix integer-overflow problem in intarray's g_int_decompress(). Tom Lane <tgl@sss.pgh.pa.us>
2024-01-07 20:20 pgsql: Fix integer-overflow problem in intarray's g_int_decompress(). Tom Lane <tgl@sss.pgh.pa.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox