x86/IRQs: correct/tighten vector check in _clear_irq_vector()

If any particular value was to be checked against, it would need to be
IRQ_VECTOR_UNASSIGNED.

Reported-by: Roger Pau Monné <roger.pau@citrix.com>

Be more strict though and use valid_irq_vector() instead.

Take the opportunity and also convert local variables to unsigned int.

Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>
This commit is contained in:
Jan Beulich committed 2019-07-22 11:45:28 +02:00
1 parent 0d7fd5f2b8
commit c6b0dad934
1 file changed
+3 -4
+3 -4
View File
@@ -283,14 +283,13 @@ void destroy_irq(unsigned int irq)
static void _clear_irq_vector(struct irq_desc *desc)
{
unsigned int cpu;
int vector, old_vector, irq = desc->irq;
unsigned int cpu, old_vector, irq = desc->irq;
unsigned int vector = desc->arch.vector;
cpumask_t tmp_mask;
BUG_ON(!desc->arch.vector);
BUG_ON(!valid_irq_vector(vector));
/* Always clear desc->arch.vector */
vector = desc->arch.vector;
cpumask_and(&tmp_mask, desc->arch.cpu_mask, &cpu_online_map);
for_each_cpu(cpu, &tmp_mask) {
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.