[dpdk-stable] [19.11 1/2] net/bnxt: fix checking VNIC in shutdown path

Somnath Kotur somnath.kotur at broadcom.com
Thu Oct 29 11:44:52 CET 2020


Oh ok... Apologies then Luca..We went by the final diff you had between the
upstream commit patch and the actual patch... perhaps that confused us or
threw us ( speaking for kalesh's 2 patches as well) off a bit ...
If they( all 4) are identical to what you already have on your sandbox,
then indeed we are good to go

Thanks a lot
Som




On Thu, 29 Oct 2020, 16:06 Luca Boccassi, <bluca at debian.org> wrote:

> On Thu, 2020-10-29 at 14:14 +0530, Somnath Kotur wrote:
> > [ backported from upstream commit
> 4b029f02de3a0ce9cdd9a3475b84ca2e42d74281 ]
> >
> > Add a couple of NULL pointer checks in bnxt_free_all_filters()
> > and bnxt_free_vnics() respectively to guard against certain error
> > injection/recovery scenarios where it was found that the application
> > was crashing with the bp->vnic_info pointer being NULL.
> >
> > Fixes: 51fafb89a9a0 ("net/bnxt: get rid of ff pools and use VNIC info
> array")
> > Cc: stable at dpdk.org
> >
> > Signed-off-by: Somnath Kotur <somnath.kotur at broadcom.com>
> > Reviewed-by: Ajit Khaparde <ajit.khaparde at broadcom.com>
> > ---
> >  drivers/net/bnxt/bnxt_filter.c | 15 +++++++++------
> >  drivers/net/bnxt/bnxt_vnic.c   |  3 +++
> >  2 files changed, 12 insertions(+), 6 deletions(-)
>
> Hi,
>
> Both of these patches appear to be 100% identical to the ones I pushed
> yesterday? Was there something unclear in the generated email that made
> you think the rebase was different that we can fix?
>
>
> https://github.com/bluca/dpdk-stable/commit/77abebfe906e80404ecdfa71c60da318cd0fb563
>
> https://github.com/bluca/dpdk-stable/commit/618bfe2417717a3b446180a10d1a2299d3f626e9
>
> --
> Kind regards,
> Luca Boccassi
>


More information about the stable mailing list