From: Ziyang Xuan <william.xuanziyang@huawei.com>
To: <vburru@marvell.com>, <aayarekar@marvell.com>,
<sburla@marvell.com>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH net 0/4] octeon_ep: fix several bugs in exception paths
Date: Fri, 11 Nov 2022 15:08:01 +0800 [thread overview]
Message-ID: <cover.1668150074.git.william.xuanziyang@huawei.com> (raw)
Find several obvious bugs during code review in exception paths. Provide
this patchset to fix them. Not tested, just compiled.
Ziyang Xuan (4):
octeon_ep: delete unnecessary napi rollback under set_queues_err in
octep_open()
octeon_ep: ensure octep_get_link_status() successfully before
octep_link_up()
octeon_ep: fix potential memory leak in octep_device_setup()
octeon_ep: ensure get mac address successfully before
eth_hw_addr_set()
.../net/ethernet/marvell/octeon_ep/octep_main.c | 16 +++++++++++-----
1 file changed, 11 insertions(+), 5 deletions(-)
--
2.25.1
next reply other threads:[~2022-11-11 7:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 7:08 Ziyang Xuan [this message]
2022-11-11 7:08 ` [PATCH net 1/4] octeon_ep: delete unnecessary napi rollback under set_queues_err in octep_open() Ziyang Xuan
2022-11-11 7:08 ` [PATCH net 2/4] octeon_ep: ensure octep_get_link_status() successfully before octep_link_up() Ziyang Xuan
2022-11-11 7:09 ` [PATCH net 3/4] octeon_ep: fix potential memory leak in octep_device_setup() Ziyang Xuan
2022-11-11 7:09 ` [PATCH net 4/4] octeon_ep: ensure get mac address successfully before eth_hw_addr_set() Ziyang Xuan
2022-11-14 11:20 ` [PATCH net 0/4] octeon_ep: fix several bugs in exception paths patchwork-bot+netdevbpf
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=cover.1668150074.git.william.xuanziyang@huawei.com \
--to=william.xuanziyang@huawei.com \
--cc=aayarekar@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sburla@marvell.com \
--cc=vburru@marvell.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
Powered by JetHome