summaryrefslogtreecommitdiff
path: root/net
diff options
context:
space:
mode:
authorJack Morgenstein <jackm@dev.mellanox.co.il>2014-11-25 11:54:31 +0200
committerDavid S. Miller <davem@davemloft.net>2014-11-26 12:04:49 -0500
commit2d5c57d7fbfaa642fb7f0673df24f32b83d9066c (patch)
tree08713831252c7124d1df3e1a7600752dc6398775 /net
parentfbe4d0d613416e4d789820bea327c2b458605b98 (diff)
downloadlinux-exynos-2d5c57d7fbfaa642fb7f0673df24f32b83d9066c.tar.gz
linux-exynos-2d5c57d7fbfaa642fb7f0673df24f32b83d9066c.tar.bz2
linux-exynos-2d5c57d7fbfaa642fb7f0673df24f32b83d9066c.zip
net/mlx4_core: Limit count field to 24 bits in qp_alloc_res
Some VF drivers use the upper byte of "param1" (the qp count field) in mlx4_qp_reserve_range() to pass flags which are used to optimize the range allocation. Under the current code, if any of these flags are set, the 32-bit count field yields a count greater than 2^24, which is out of range, and this VF fails. As these flags represent a "best-effort" allocation hint anyway, they may safely be ignored. Therefore, the PF driver may simply mask out the bits. Fixes: c82e9aa0a8 "mlx4_core: resource tracking for HCA resources used by guests" Signed-off-by: Jack Morgenstein <jackm@dev.mellanox.co.il> Signed-off-by: Or Gerlitz <ogerlitz@mellanox.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions