From 0e23c487dad7a1bd9b2cff409144910386823c15 Mon Sep 17 00:00:00 2001
From: James Zern <jzern@google.com>
Date: Thu, 11 Sep 2014 15:26:11 -0700
Subject: [PATCH] webpmux: fix loop_count range check

explicitly check [0, 65535], the use of 'long' was removed in a prior
commit

Change-Id: I70d5bf286908459b5d4d619c657853f0e833b6ea
---
 examples/webpmux.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/examples/webpmux.c b/examples/webpmux.c
index f3874920..5fa5387a 100644
--- a/examples/webpmux.c
+++ b/examples/webpmux.c
@@ -939,7 +939,7 @@ static int Process(const WebPMuxConfig* config) {
                 int parse_error = 0;
                 const int loop_count =
                     ExUtilGetInt(feature->args_[i].params_, 10, &parse_error);
-                if (loop_count != (int)loop_count) {
+                if (loop_count < 0 || loop_count > 65535) {
                   // Note: This is only a 'necessary' condition for loop_count
                   // to be valid. The 'sufficient' conditioned in checked in
                   // WebPMuxSetAnimationParams() method called later.