Doron Tsur 0b6e26ce89 net/mlx5_core: Fix trimming down IRQ number
With several ConnectX-4 cards installed on a server, one may receive
irqn > 255 from the kernel API, which we mistakenly trim to 8bit.

This causes EQ creation failure with the following stack trace:
[<ffffffff812a11f4>] dump_stack+0x48/0x64
[<ffffffff810ace21>] __setup_irq+0x3a1/0x4f0
[<ffffffff810ad7e0>] request_threaded_irq+0x120/0x180
[<ffffffffa0923660>] ? mlx5_eq_int+0x450/0x450 [mlx5_core]
[<ffffffffa0922f64>] mlx5_create_map_eq+0x1e4/0x2b0 [mlx5_core]
[<ffffffffa091de01>] alloc_comp_eqs+0xb1/0x180 [mlx5_core]
[<ffffffffa091ea99>] mlx5_dev_init+0x5e9/0x6e0 [mlx5_core]
[<ffffffffa091ec29>] init_one+0x99/0x1c0 [mlx5_core]
[<ffffffff812e2afc>] local_pci_probe+0x4c/0xa0

Fixing it by changing of the irqn type from u8 to unsigned int to
support values > 255

Fixes: 61d0e73e0a5a ('net/mlx5_core: Use the the real irqn in eq->irqn')
Reported-by: Jiri Pirko <jiri@mellanox.com>
Signed-off-by: Doron Tsur <doront@mellanox.com>
Signed-off-by: Matan Barak <matanb@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2016-01-17 12:08:04 -05:00
..
2016-01-13 19:15:14 -08:00
2015-12-29 15:32:24 -05:00
2015-12-12 16:43:44 -08:00
2016-01-15 13:18:47 -08:00
2016-01-15 13:18:47 -08:00
2016-01-15 13:18:47 -08:00
2016-01-13 10:59:52 -08:00
2016-01-01 18:31:34 +01:00
2015-12-21 11:44:00 +09:00
2016-01-14 10:53:15 -08:00
2016-01-13 10:23:36 -08:00
2016-01-12 12:17:28 +01:00
2016-01-15 12:28:00 -08:00
2016-01-14 10:53:15 -08:00
2016-01-15 13:18:47 -08:00
2016-01-05 18:04:58 +01:00
2016-01-13 11:25:54 -08:00
2016-01-14 11:13:28 -08:00
2016-01-03 16:32:59 -08:00
2015-12-26 17:01:18 -08:00
2016-01-12 01:12:40 +01:00
2016-01-15 12:14:47 -08:00
2016-01-15 13:18:47 -08:00
2016-01-13 19:37:36 -08:00
2016-01-15 13:18:47 -08:00
2016-01-15 13:18:47 -08:00
2016-01-15 13:18:47 -08:00
2016-01-15 13:18:47 -08:00
2015-12-01 14:26:33 -08:00
2016-01-14 10:34:33 -08:00
2016-01-07 13:21:53 +00:00