[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180726024037.28704-1-jakub.kicinski@netronome.com>
Date: Wed, 25 Jul 2018 19:40:33 -0700
From: Jakub Kicinski <jakub.kicinski@...ronome.com>
To: davem@...emloft.net
Cc: oss-drivers@...ronome.com, netdev@...r.kernel.org,
Jakub Kicinski <jakub.kicinski@...ronome.com>
Subject: [PATCH net-next 0/4] nfp: protect from theoretical size overflows and SR-IOV errors
Hi!
This small set changes the handling of pci_sriov_set_totalvfs() errors.
nfp is the only driver which fails probe on pci_sriov_set_totalvfs()
errors. It turns out some BIOS configurations may break SR-IOV and
users who don't use that feature should not suffer.
Remaining patches makes sure we use overflow-safe function for ring
allocation, even though ring sizes are limited. It won't hurt and
we can also enable fallback to vmalloc() if memory is tight while
at it.
Jakub Kicinski (4):
nfp: don't fail probe on pci_sriov_set_totalvfs() errors
nfp: use kvcalloc() to allocate SW buffer descriptor arrays
nfp: restore correct ordering of fields in rx ring structure
nfp: protect from theoretical size overflows on HW descriptor ring
drivers/net/ethernet/netronome/nfp/nfp_main.c | 20 +++++++++------
drivers/net/ethernet/netronome/nfp/nfp_net.h | 9 ++++---
.../ethernet/netronome/nfp/nfp_net_common.c | 25 ++++++++++---------
3 files changed, 30 insertions(+), 24 deletions(-)
--
2.17.1
Powered by blists - more mailing lists