From: David Miller <davem@davemloft.net>
To: mironov.ivan@gmail.com
Cc: netdev@vger.kernel.org, ariel.elior@cavium.com,
sudarsana.kalluru@cavium.com, everest-linux-l2@cavium.com,
linux-kernel@vger.kernel.org, skalluru@marvell.com
Subject: Re: [PATCH v2] bnx2x: Fix NULL pointer dereference in bnx2x_del_all_vlans() on some hw
Date: Mon, 24 Dec 2018 14:46:35 -0800 (PST) [thread overview]
Message-ID: <20181224.144635.854624726050744324.davem@davemloft.net> (raw)
In-Reply-To: <20181224151305.31027-1-mironov.ivan@gmail.com>
From: Ivan Mironov <mironov.ivan@gmail.com>
Date: Mon, 24 Dec 2018 20:13:05 +0500
> This happened when I tried to boot normal Fedora 29 system with latest
> available kernel (from fedora rawhide, plus some unrelated custom
> patches):
...
> After some investigation I figured out that recently added cleanup code
> tries to call VLAN filtering de-initialization function which exist only
> for newer hardware. Corresponding function pointer is not
> set (== 0) for older hardware, namely these chips:
>
> #define CHIP_NUM_57710 0x164e
> #define CHIP_NUM_57711 0x164f
> #define CHIP_NUM_57711E 0x1650
>
> And I have one of those in my test system:
>
> Broadcom Inc. and subsidiaries NetXtreme II BCM57711E 10-Gigabit PCIe [14e4:1650]
>
> Function bnx2x_init_vlan_mac_fp_objs() from
> drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.h decides whether to
> initialize relevant pointers in bnx2x_sp_objs.vlan_obj or not.
>
> This regression was introduced after v4.20-rc7, and still exists in v4.20
> release.
>
> Fixes: 04f05230c5c13 ("bnx2x: Remove configured vlans as part of unload sequence.")
> Signed-off-by: Ivan Mironov <mironov.ivan@gmail.com>
Applied, thanks.
prev parent reply other threads:[~2018-12-24 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-24 15:13 [PATCH v2] bnx2x: Fix NULL pointer dereference in bnx2x_del_all_vlans() on some hw Ivan Mironov
2018-12-24 16:06 ` [EXT] " Sudarsana Reddy Kalluru
2018-12-24 22:46 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181224.144635.854624726050744324.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ariel.elior@cavium.com \
--cc=everest-linux-l2@cavium.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mironov.ivan@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=skalluru@marvell.com \
--cc=sudarsana.kalluru@cavium.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox