From: Michael Chan <michael.chan@broadcom.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, gospo@broadcom.com
Subject: [PATCH net 0/2] bnxt_en: 2 bug fixes
Date: Fri, 3 Mar 2023 18:43:56 -0800 [thread overview]
Message-ID: <1677897838-23562-1-git-send-email-michael.chan@broadcom.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
This series fixes 2 issues:
1. A potential order-5 memory allocation failure during open.
2. Double memory free bug during shutdown.
Michael Chan (1):
bnxt_en: Avoid order-5 memory allocation for TPA data
Selvin Xavier (1):
bnxt_en: Fix the double free during device removal
drivers/net/ethernet/broadcom/bnxt/bnxt.c | 25 +++++++++----------
drivers/net/ethernet/broadcom/bnxt/bnxt_ulp.c | 2 ++
2 files changed, 14 insertions(+), 13 deletions(-)
--
2.32.0
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4209 bytes --]
next reply other threads:[~2023-03-04 2:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 2:43 Michael Chan [this message]
2023-03-04 2:43 ` [PATCH net 1/2] bnxt_en: Avoid order-5 memory allocation for TPA data Michael Chan
2023-03-04 2:43 ` [PATCH net 2/2] bnxt_en: Fix the double free during device removal Michael Chan
2023-03-06 21:30 ` [PATCH net 0/2] bnxt_en: 2 bug fixes patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2021-08-15 20:15 Michael Chan
2021-08-16 10:40 ` patchwork-bot+netdevbpf
2021-05-15 7:25 Michael Chan
2021-05-17 21:10 ` patchwork-bot+netdevbpf
2021-02-11 7:24 Michael Chan
2021-02-11 22:50 ` patchwork-bot+netdevbpf
2020-03-02 3:07 Michael Chan
2020-03-02 3:17 ` David Miller
2019-04-08 21:39 Michael Chan
2019-04-08 23:39 ` David Miller
2016-11-11 5:11 Michael Chan
2016-11-13 17:37 ` David Miller
2016-05-04 20:56 Michael Chan
2016-05-04 21:12 ` David Miller
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=1677897838-23562-1-git-send-email-michael.chan@broadcom.com \
--to=michael.chan@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gospo@broadcom.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.