IB/hfi1: Stricter bounds checking of MAD trap index
The macro size is valid. This change makes it less ambiguous. Bounds check trap type for better security. Reviewed-by: Michael J. Ruhl <michael.j.ruhl@intel.com> Signed-off-by: Kamenee Arumugam <kamenee.arumugam@intel.com> Signed-off-by: Dennis Dalessandro <dennis.dalessandro@intel.com> Signed-off-by: Doug Ledford <dledford@redhat.com>
This commit is contained in:

committed by
Doug Ledford

parent
76ae6222a4
commit
ec0d8b8a63
@@ -64,7 +64,7 @@
|
||||
#define RVT_MAX_PKEY_VALUES 16
|
||||
|
||||
#define RVT_MAX_TRAP_LEN 100 /* Limit pending trap list */
|
||||
#define RVT_MAX_TRAP_LISTS ((IB_NOTICE_TYPE_INFO & 0x0F) + 1)
|
||||
#define RVT_MAX_TRAP_LISTS 5 /*((IB_NOTICE_TYPE_INFO & 0x0F) + 1)*/
|
||||
#define RVT_TRAP_TIMEOUT 4096 /* 4.096 usec */
|
||||
|
||||
struct trap_list {
|
||||
|
Reference in New Issue
Block a user