irqchip/gic-v3-its: Fix comparison logic in lpi_range_cmp
authorRasmus Villemoes <linux@rasmusvillemoes.dk>
Tue, 12 Mar 2019 17:33:46 +0000 (18:33 +0100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 27 Mar 2019 05:14:40 +0000 (14:14 +0900)
commitaacf2cc814c2dc45494945c4c485abe8699a3a50
treede5b2bd70e1a2c4645dd66ea517f69ad513e11ce
parentdaaeeca918e726bda1681a34196437819821bc7f
irqchip/gic-v3-its: Fix comparison logic in lpi_range_cmp

commit 89dc891792c2e046b030f87600109c22209da32e upstream.

The lpi_range_list is supposed to be sorted in ascending order of
->base_id (at least if the range merging is to work), but the current
comparison function returns a positive value if rb->base_id >
ra->base_id, which means that list_sort() will put A after B in that
case - and vice versa, of course.

Fixes: 880cb3cddd16 (irqchip/gic-v3-its: Refactor LPI allocator)
Cc: stable@vger.kernel.org (v4.19+)
Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/irqchip/irq-gic-v3-its.c