summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPrasad J Pandit <pjp@fedoraproject.org>2015-12-03 18:54:17 +0530
committerPeter Maydell <peter.maydell@linaro.org>2015-12-03 13:34:50 +0000
commit4c65fed8bdf96780735dbdb92a8bd0d6b6526cc3 (patch)
tree2c571142f1fbe400a24f6a77e8e86618d465272e
parentefdeb96c5a1179ee3fde3a0d77fb19f92e5849e5 (diff)
downloadhqemu-4c65fed8bdf96780735dbdb92a8bd0d6b6526cc3.zip
hqemu-4c65fed8bdf96780735dbdb92a8bd0d6b6526cc3.tar.gz
ui: vnc: avoid floating point exception
While sending 'SetPixelFormat' messages to a VNC server, the client could set the 'red-max', 'green-max' and 'blue-max' values to be zero. This leads to a floating point exception in write_png_palette while doing frame buffer updates. Reported-by: Lian Yihan <lianyihan@360.cn> Signed-off-by: Prasad J Pandit <pjp@fedoraproject.org> Reviewed-by: Gerd Hoffmann <kraxel@redhat.com> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
-rw-r--r--ui/vnc.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/ui/vnc.c b/ui/vnc.c
index 7538405..cbe4d33 100644
--- a/ui/vnc.c
+++ b/ui/vnc.c
@@ -2198,15 +2198,15 @@ static void set_pixel_format(VncState *vs,
return;
}
- vs->client_pf.rmax = red_max;
+ vs->client_pf.rmax = red_max ? red_max : 0xFF;
vs->client_pf.rbits = hweight_long(red_max);
vs->client_pf.rshift = red_shift;
vs->client_pf.rmask = red_max << red_shift;
- vs->client_pf.gmax = green_max;
+ vs->client_pf.gmax = green_max ? green_max : 0xFF;
vs->client_pf.gbits = hweight_long(green_max);
vs->client_pf.gshift = green_shift;
vs->client_pf.gmask = green_max << green_shift;
- vs->client_pf.bmax = blue_max;
+ vs->client_pf.bmax = blue_max ? blue_max : 0xFF;
vs->client_pf.bbits = hweight_long(blue_max);
vs->client_pf.bshift = blue_shift;
vs->client_pf.bmask = blue_max << blue_shift;
OpenPOWER on IntegriCloud