From: Shang XiaoJing <shangxiaojing@huawei.com>
To: <horatiu.vultur@microchip.com>, <UNGLinuxDriver@microchip.com>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <lars.povlsen@microchip.com>,
<Steen.Hegelund@microchip.com>, <daniel.machon@microchip.com>,
<rmk+kernel@armlinux.org.uk>, <casper.casan@gmail.com>,
<bjarni.jonasson@microchip.com>, <netdev@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Cc: <shangxiaojing@huawei.com>
Subject: [PATCH 0/2] net: microchip: Fix potential null-ptr-deref due to create_singlethread_workqueue()
Date: Mon, 14 Nov 2022 21:38:51 +0800 [thread overview]
Message-ID: <20221114133853.5384-1-shangxiaojing@huawei.com> (raw)
There are some functions call create_singlethread_workqueue() without
checking ret value, and the NULL workqueue_struct pointer may causes
null-ptr-deref. Will be fixed by this patch.
Shang XiaoJing (2):
net: lan966x: Fix potential null-ptr-deref in lan966x_stats_init()
net: microchip: sparx5: Fix potential null-ptr-deref in
sparx_stats_init() and sparx5_start()
drivers/net/ethernet/microchip/lan966x/lan966x_ethtool.c | 3 +++
drivers/net/ethernet/microchip/sparx5/sparx5_ethtool.c | 3 +++
drivers/net/ethernet/microchip/sparx5/sparx5_main.c | 3 +++
3 files changed, 9 insertions(+)
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-11-14 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 13:38 Shang XiaoJing [this message]
2022-11-14 13:38 ` [PATCH 1/2] net: lan966x: Fix potential null-ptr-deref in lan966x_stats_init() Shang XiaoJing
2022-11-14 14:20 ` Horatiu Vultur
2022-11-14 13:38 ` [PATCH 2/2] net: microchip: sparx5: Fix potential null-ptr-deref in sparx_stats_init() and sparx5_start() Shang XiaoJing
2022-11-16 9:20 ` [PATCH 0/2] net: microchip: Fix potential null-ptr-deref due to create_singlethread_workqueue() 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=20221114133853.5384-1-shangxiaojing@huawei.com \
--to=shangxiaojing@huawei.com \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=bjarni.jonasson@microchip.com \
--cc=casper.casan@gmail.com \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
/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