summaryrefslogtreecommitdiffstats
path: root/common/msg.c
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2014-01-29 17:01:42 +0100
committerwm4 <wm4@nowhere>2014-01-29 17:01:42 +0100
commit8e61e9ed6e549cfb4ad0180a2ed20d9a2f10fcdc (patch)
tree3698d79834e18f8b021ac236a8681ab5dbfcc173 /common/msg.c
parent46c9dfe2e7f2b8e2e1fb4a1ef0bb9de0bdd5a8b3 (diff)
downloadmpv-8e61e9ed6e549cfb4ad0180a2ed20d9a2f10fcdc.tar.bz2
mpv-8e61e9ed6e549cfb4ad0180a2ed20d9a2f10fcdc.tar.xz
mp_image: reject too large image sizes
Larger sizes can introduce overflows, depending on the image format. In the worst case, something larger than 16000x16000 with 8 bytes per pixel will overflow 31 bits. Maybe there should be a proper failure path instead of a hard crash, but not yet. I imagine anything that sets a higher image size than a known working size should be forced to call a function to check the size (much like in ffmpeg/libavutil).
Diffstat (limited to 'common/msg.c')
0 files changed, 0 insertions, 0 deletions