netdev - re: net/mlx4_core: Capping number of requested MSIXs to MAX

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Date:	Sat, 29 Aug 2015 23:36:52 -0700
From:	Or Gerlitz <gerlitz.or@...il.com>
To:	Carol L Soto <clsoto@...ux.vnet.ibm.com>,
	Matan Barak <matanb@...lanox.com>
Cc:	Linux Netdev List <netdev@...r.kernel.org>,
	Amir Vadai <amirv@...lanox.com>
Subject: re: net/mlx4_core: Capping number of requested MSIXs to MAX_MSIX

> We currently manage IRQs in pool_bm which is a bit field of MAX_MSIX bits.
> Thus, allocating more than MAX_MSIX interrupts can't be managed in pool_bm.
> Fixing this by capping number of requested MSIXs to MAX_MSIX.

Carol, Matan, could U2 elaborate where/when the bug hits us?


Also, missing Fixes: line here with the offending commit ID so we can
realize if this needs to go into -stable

> Signed-off-by: Matan Barak <matanb@...lanox.com>
> Signed-off-by: Carol L Soto <clsoto@...ux.vnet.ibm.com>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html