From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: Pavel Skripkin <paskripkin@gmail.com>, <davem@davemloft.net>,
<kuba@kernel.org>, <qiangqing.zhang@nxp.com>,
<hslester96@gmail.com>, <fugang.duan@nxp.com>, <jdmason@kudzu.us>,
<colin.king@canonical.com>
Cc: <dan.carpenter@oracle.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] net: fix use-after-free bugs
Date: Wed, 4 Aug 2021 11:38:05 -0700 [thread overview]
Message-ID: <b30b28c5-5e96-6f5e-a43d-141419dda6ae@intel.com> (raw)
In-Reply-To: <cover.1628091954.git.paskripkin@gmail.com>
On 8/4/2021 8:48 AM, Pavel Skripkin wrote:
> I've added new checker to smatch yesterday. It warns about using
> netdev_priv() pointer after free_{netdev,candev}() call. I hope, it will
> get into next smatch release.
>
> Some of the reported bugs are fixed and upstreamed already, but Dan ran new
> smatch with allmodconfig and found 2 more. Big thanks to Dan for doing it,
> because I totally forgot to do it.
>
> Pavel Skripkin (2):
> net: fec: fix use-after-free in fec_drv_remove
> net: vxge: fix use-after-free in vxge_device_unregister
>
> drivers/net/ethernet/freescale/fec_main.c | 2 +-
> drivers/net/ethernet/neterion/vxge/vxge-main.c | 6 +++---
> 2 files changed, 4 insertions(+), 4 deletions(-)
Looks like a good new check! For the series:
Reviewed-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
next prev parent reply other threads:[~2021-08-04 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 15:48 [PATCH 0/2] net: fix use-after-free bugs Pavel Skripkin
2021-08-04 15:51 ` [PATCH 1/2] net: fec: fix use-after-free in fec_drv_remove Pavel Skripkin
2021-08-05 2:24 ` Joakim Zhang
2021-08-04 15:52 ` [PATCH 2/2] net: vxge: fix use-after-free in vxge_device_unregister Pavel Skripkin
2021-08-04 18:38 ` Jesse Brandeburg [this message]
2021-08-05 14:50 ` [PATCH 0/2] net: fix use-after-free bugs 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=b30b28c5-5e96-6f5e-a43d-141419dda6ae@intel.com \
--to=jesse.brandeburg@intel.com \
--cc=colin.king@canonical.com \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=fugang.duan@nxp.com \
--cc=hslester96@gmail.com \
--cc=jdmason@kudzu.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paskripkin@gmail.com \
--cc=qiangqing.zhang@nxp.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.