pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Catch stack overflow when recursing in transformFromClauseItem() 7+ messages / 1 participants [nested] [flat]
* pgsql: Catch stack overflow when recursing in transformFromClauseItem() @ 2022-08-13 19:21 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 7+ messages in thread From: Tom Lane @ 2022-08-13 19:21 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Catch stack overflow when recursing in transformFromClauseItem(). Most parts of the parser can expect that the stack overflow check in transformExprRecurse() will trigger before things get desperate. However, transformFromClauseItem() can recurse directly to self without having analyzed any expressions, so it's possible to drive it to a stack-overrun crash. Add a check to prevent that. Per bug #17583 from Egor Chindyaskin. Back-patch to all supported branches. Richard Guo Discussion: https://postgr.es/m/17583-33be55b9f981f75c@postgresql.org Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/e07ebd4b6e606a7c03ed3c6bf5d6bcbb725247b4 Modified Files -------------- src/backend/parser/parse_clause.c | 3 +++ 1 file changed, 3 insertions(+) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Catch stack overflow when recursing in transformFromClauseItem() @ 2022-08-13 19:21 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 7+ messages in thread From: Tom Lane @ 2022-08-13 19:21 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Catch stack overflow when recursing in transformFromClauseItem(). Most parts of the parser can expect that the stack overflow check in transformExprRecurse() will trigger before things get desperate. However, transformFromClauseItem() can recurse directly to self without having analyzed any expressions, so it's possible to drive it to a stack-overrun crash. Add a check to prevent that. Per bug #17583 from Egor Chindyaskin. Back-patch to all supported branches. Richard Guo Discussion: https://postgr.es/m/17583-33be55b9f981f75c@postgresql.org Branch ------ REL_15_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/00ac61695e5c7d573b14bb7a61387a3fae017928 Modified Files -------------- src/backend/parser/parse_clause.c | 3 +++ 1 file changed, 3 insertions(+) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Catch stack overflow when recursing in transformFromClauseItem() @ 2022-08-13 19:21 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 7+ messages in thread From: Tom Lane @ 2022-08-13 19:21 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Catch stack overflow when recursing in transformFromClauseItem(). Most parts of the parser can expect that the stack overflow check in transformExprRecurse() will trigger before things get desperate. However, transformFromClauseItem() can recurse directly to self without having analyzed any expressions, so it's possible to drive it to a stack-overrun crash. Add a check to prevent that. Per bug #17583 from Egor Chindyaskin. Back-patch to all supported branches. Richard Guo Discussion: https://postgr.es/m/17583-33be55b9f981f75c@postgresql.org Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/496ab1d6c8d853899595e986f04cd70c4b13dac4 Modified Files -------------- src/backend/parser/parse_clause.c | 3 +++ 1 file changed, 3 insertions(+) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Catch stack overflow when recursing in transformFromClauseItem() @ 2022-08-13 19:21 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 7+ messages in thread From: Tom Lane @ 2022-08-13 19:21 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Catch stack overflow when recursing in transformFromClauseItem(). Most parts of the parser can expect that the stack overflow check in transformExprRecurse() will trigger before things get desperate. However, transformFromClauseItem() can recurse directly to self without having analyzed any expressions, so it's possible to drive it to a stack-overrun crash. Add a check to prevent that. Per bug #17583 from Egor Chindyaskin. Back-patch to all supported branches. Richard Guo Discussion: https://postgr.es/m/17583-33be55b9f981f75c@postgresql.org Branch ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/60f876317efc7b9ad624b11ae2f4b8208e408ef4 Modified Files -------------- src/backend/parser/parse_clause.c | 3 +++ 1 file changed, 3 insertions(+) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Catch stack overflow when recursing in transformFromClauseItem() @ 2022-08-13 19:21 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 7+ messages in thread From: Tom Lane @ 2022-08-13 19:21 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Catch stack overflow when recursing in transformFromClauseItem(). Most parts of the parser can expect that the stack overflow check in transformExprRecurse() will trigger before things get desperate. However, transformFromClauseItem() can recurse directly to self without having analyzed any expressions, so it's possible to drive it to a stack-overrun crash. Add a check to prevent that. Per bug #17583 from Egor Chindyaskin. Back-patch to all supported branches. Richard Guo Discussion: https://postgr.es/m/17583-33be55b9f981f75c@postgresql.org Branch ------ REL_12_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/ba516fb0715c75b1b2d393c3de7b99fca6a1ac67 Modified Files -------------- src/backend/parser/parse_clause.c | 3 +++ 1 file changed, 3 insertions(+) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Catch stack overflow when recursing in transformFromClauseItem() @ 2022-08-13 19:21 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 7+ messages in thread From: Tom Lane @ 2022-08-13 19:21 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Catch stack overflow when recursing in transformFromClauseItem(). Most parts of the parser can expect that the stack overflow check in transformExprRecurse() will trigger before things get desperate. However, transformFromClauseItem() can recurse directly to self without having analyzed any expressions, so it's possible to drive it to a stack-overrun crash. Add a check to prevent that. Per bug #17583 from Egor Chindyaskin. Back-patch to all supported branches. Richard Guo Discussion: https://postgr.es/m/17583-33be55b9f981f75c@postgresql.org Branch ------ REL_11_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/b744e13b021712d4aae3c239e8aedefc463c755f Modified Files -------------- src/backend/parser/parse_clause.c | 3 +++ 1 file changed, 3 insertions(+) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Catch stack overflow when recursing in transformFromClauseItem() @ 2022-08-13 19:21 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 7+ messages in thread From: Tom Lane @ 2022-08-13 19:21 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Catch stack overflow when recursing in transformFromClauseItem(). Most parts of the parser can expect that the stack overflow check in transformExprRecurse() will trigger before things get desperate. However, transformFromClauseItem() can recurse directly to self without having analyzed any expressions, so it's possible to drive it to a stack-overrun crash. Add a check to prevent that. Per bug #17583 from Egor Chindyaskin. Back-patch to all supported branches. Richard Guo Discussion: https://postgr.es/m/17583-33be55b9f981f75c@postgresql.org Branch ------ REL_10_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/362032f1768e0c0792fb713234ea1db2ebfaf90d Modified Files -------------- src/backend/parser/parse_clause.c | 3 +++ 1 file changed, 3 insertions(+) ^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2022-08-13 19:21 UTC | newest] Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2022-08-13 19:21 pgsql: Catch stack overflow when recursing in transformFromClauseItem() Tom Lane <tgl@sss.pgh.pa.us> 2022-08-13 19:21 pgsql: Catch stack overflow when recursing in transformFromClauseItem() Tom Lane <tgl@sss.pgh.pa.us> 2022-08-13 19:21 pgsql: Catch stack overflow when recursing in transformFromClauseItem() Tom Lane <tgl@sss.pgh.pa.us> 2022-08-13 19:21 pgsql: Catch stack overflow when recursing in transformFromClauseItem() Tom Lane <tgl@sss.pgh.pa.us> 2022-08-13 19:21 pgsql: Catch stack overflow when recursing in transformFromClauseItem() Tom Lane <tgl@sss.pgh.pa.us> 2022-08-13 19:21 pgsql: Catch stack overflow when recursing in transformFromClauseItem() Tom Lane <tgl@sss.pgh.pa.us> 2022-08-13 19:21 pgsql: Catch stack overflow when recursing in transformFromClauseItem() 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