From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next 0/4] nfp: protect from theoretical size overflows and SR-IOV errors Date: Wed, 25 Jul 2018 22:18:01 -0700 (PDT) Message-ID: <20180725.221801.2029165624240760094.davem@davemloft.net> References: <20180726024037.28704-1-jakub.kicinski@netronome.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: oss-drivers@netronome.com, netdev@vger.kernel.org To: jakub.kicinski@netronome.com Return-path: Received: from shards.monkeyblade.net ([23.128.96.9]:33102 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727070AbeGZGdJ (ORCPT ); Thu, 26 Jul 2018 02:33:09 -0400 In-Reply-To: <20180726024037.28704-1-jakub.kicinski@netronome.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Jakub Kicinski Date: Wed, 25 Jul 2018 19:40:33 -0700 > 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. Series applied, thanks Jakub.