On Thu, Oct 15, 2020 at 10:22 PM Eduardo Habkost <ehabk...@redhat.com> wrote: > > On Mon, Sep 21, 2020 at 03:03:25PM +0530, Ani Sinha wrote: > > Object property insertion code iterates over an integer to get an unused > > index that can be used as an unique name for an object property. This loop > > increments the integer value indefinitely. Although very unlikely, this can > > still cause an integer overflow. > > In this change, we fix the above code by checking against INT16_MAX and > > making > > sure that the interger index does not overflow beyond that value. If no > > available index is found, the code would cause an assertion failure. This > > assertion failure is necessary because the callers of the function do not > > check > > the return value for NULL. > > > > Signed-off-by: Ani Sinha <a...@anisinha.ca> > > Reviewed-by: Daniel P. Berrangé <berra...@redhat.com> > > Queued on machine-next, thanks! My apologies for the delay.
Any idea when this will be pulled?
