mirror of
https://github.com/postgres/postgres.git
synced 2026-04-08 18:51:56 -04:00
9ed207ae99
Some of the functions in regex compilation and execution recurse, and therefore could in principle be driven to stack overflow. The Tcl crew has seen this happen in practice in duptraverse(), though their fix was to put in a hard-wired limit on the number of recursive levels, which is not too appetizing --- fortunately, we have enough infrastructure to check the actually available stack. Greg Stark has also seen it in other places while fuzz testing on a machine with limited stack space. Let's put guards in to prevent crashes in all these places. Since the regex code would leak memory if we simply threw elog(ERROR), we have to introduce an API that checks for stack depth without throwing such an error. Fortunately that's not difficult. |
||
|---|---|---|
| .. | ||
| regcustom.h | ||
| regerrs.h | ||
| regex.h | ||
| regexport.h | ||
| regguts.h | ||