summaryrefslogtreecommitdiff
path: root/appveyor.yml
diff options
context:
space:
mode:
authorVicențiu Ciorbaru <vicentiu@mariadb.org>2020-10-23 18:09:01 +0300
committerVicențiu Ciorbaru <vicentiu@mariadb.org>2020-10-26 21:02:13 +0200
commit858434910835117215890f8368b91b2905e74815 (patch)
tree4bd35a0d05af443182ebfc3e69e058e3080eb8c1 /appveyor.yml
parent44c958dd7b454ebbdbf7ac8b066592c82dd3409f (diff)
downloadmariadb-git-858434910835117215890f8368b91b2905e74815.tar.gz
MDEV-14945 possible buffer overflow in stack resolver
According to https://stackoverflow.com/questions/22827510/how-to-avoid-bad-fd-set-buffer-overflow-crash it seems that using select instead of poll can cause additional memory allocations. As we are in a crashed state, we must prevent allocating any memory (if possible). Thus, switch select call to poll. Also move some bigger datastructures to global space. The code is not run in a multithreaded context so best we don't use up stack space if it's not needed.
Diffstat (limited to 'appveyor.yml')
0 files changed, 0 insertions, 0 deletions