From: Shinas Rasheed <srasheed@marvell.com>
To: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <hgani@marvell.com>, <sedara@marvell.com>, <vimleshk@marvell.com>,
<thaller@redhat.com>, <wizhao@redhat.com>, <kheib@redhat.com>,
<egallen@redhat.com>, <konguyen@redhat.com>, <horms@kernel.org>,
"Shinas Rasheed" <srasheed@marvell.com>
Subject: [PATCH net v4 0/7] Double free fixes and NULL pointer checks
Date: Wed, 13 Nov 2024 03:13:12 -0800 [thread overview]
Message-ID: <20241113111319.1156507-1-srasheed@marvell.com> (raw)
Fix double frees which happen on reset scenarios, and add
NULL pointer checks for when rare cases might trigger
dereferences of such.
Changes:
V4:
- Removed unnecessary protective code from octep_disable_msix() and
improved commit message
V3: https://lore.kernel.org/all/20241108074543.1123036-1-srasheed@marvell.com/
- Added back "fixes" to the Changes listed
V2: https://lore.kernel.org/all/20241107132846.1118835-1-srasheed@marvell.com/
- Added more context in commit messages and split patches for each
commit fix
V1: https://lore.kernel.org/all/20241101103416.1064930-1-srasheed@marvell.com/
Shinas Rasheed (6):
octeon_ep: Fix null dereferences to IQ/OQ pointers
octeon_ep: add protective null checks in napi callbacks for cn9k cards
octeon_ep: add protective null checks in napi callbacks for cnxk cards
octeon_ep_vf: Fix null dereferences to IQ/OQ pointers
octeon_ep_vf: add protective null checks in napi callbacks for cn9k
cards
octeon_ep_vf: add protective null checks in napi callbacks for cnxk
cards
Vimlesh Kumar (1):
octeon_ep: Add checks to fix double free crashes
.../ethernet/marvell/octeon_ep/octep_cn9k_pf.c | 9 ++++++++-
.../ethernet/marvell/octeon_ep/octep_cnxk_pf.c | 9 ++++++++-
.../net/ethernet/marvell/octeon_ep/octep_main.c | 17 +++++++++++++----
.../net/ethernet/marvell/octeon_ep/octep_tx.c | 2 ++
.../marvell/octeon_ep_vf/octep_vf_cn9k.c | 8 +++++++-
.../marvell/octeon_ep_vf/octep_vf_cnxk.c | 12 +++++++++++-
.../marvell/octeon_ep_vf/octep_vf_main.c | 3 +++
7 files changed, 52 insertions(+), 8 deletions(-)
--
2.25.1
next reply other threads:[~2024-11-13 11:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 11:13 Shinas Rasheed [this message]
2024-11-13 11:13 ` [PATCH net v4 1/7] octeon_ep: Add checks to fix double free crashes Shinas Rasheed
2024-11-13 14:59 ` Vadim Fedorenko
2024-11-13 22:38 ` Vadim Fedorenko
2024-11-16 17:25 ` [EXTERNAL] " Shinas Rasheed
2024-11-13 11:13 ` [PATCH net v4 2/7] octeon_ep: Fix null dereferences to IQ/OQ pointers Shinas Rasheed
2024-11-13 11:13 ` [PATCH net v4 3/7] octeon_ep: add protective null checks in napi callbacks for cn9k cards Shinas Rasheed
2024-11-13 17:59 ` Vadim Fedorenko
2024-11-13 11:13 ` [PATCH net v4 4/7] octeon_ep: add protective null checks in napi callbacks for cnxk cards Shinas Rasheed
2024-11-13 18:01 ` Vadim Fedorenko
2024-11-13 11:13 ` [PATCH net v4 5/7] octeon_ep_vf: Fix null dereferences to IQ/OQ pointers Shinas Rasheed
2024-11-13 11:13 ` [PATCH net v4 6/7] octeon_ep_vf: add protective null checks in napi callbacks for cn9k cards Shinas Rasheed
2024-11-13 18:02 ` Vadim Fedorenko
2024-11-13 11:13 ` [PATCH net v4 7/7] octeon_ep_vf: add protective null checks in napi callbacks for cnxk cards Shinas Rasheed
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=20241113111319.1156507-1-srasheed@marvell.com \
--to=srasheed@marvell.com \
--cc=egallen@redhat.com \
--cc=hgani@marvell.com \
--cc=horms@kernel.org \
--cc=kheib@redhat.com \
--cc=konguyen@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sedara@marvell.com \
--cc=thaller@redhat.com \
--cc=vimleshk@marvell.com \
--cc=wizhao@redhat.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;
as well as URLs for NNTP newsgroup(s).