From: Simon Horman <simon.horman@corigine.com>
To: Zheng Wang <zyytlz.wz@163.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, petrm@nvidia.com, thomas.lendacky@amd.com,
wsa+renesas@sang-engineering.com, leon@kernel.org,
shayagr@amazon.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, hackerzheng666@gmail.com,
1395428693sheep@gmail.com, alex000young@gmail.com
Subject: Re: [PATCH net] xirc2ps_cs: Fix use after free bug in xirc2ps_detach
Date: Fri, 10 Mar 2023 14:58:52 +0100 [thread overview]
Message-ID: <ZAs3nOoT0GmsLfGN@corigine.com> (raw)
In-Reply-To: <20230309165729.164440-1-zyytlz.wz@163.com>
On Fri, Mar 10, 2023 at 12:57:29AM +0800, Zheng Wang wrote:
> In xirc2ps_probe, the local->tx_timeout_task was bounded
> with xirc2ps_tx_timeout_task. When timeout occurs,
> it will call xirc_tx_timeout->schedule_work to start the
> work.
>
> When we call xirc2ps_detach to remove the driver, there
> may be a sequence as follows:
>
> Fix it by finishing the work before cleanup in xirc2ps_detach
>
> CPU0 CPU1
>
> |xirc2ps_tx_timeout_task
> xirc2ps_detach |
> free_netdev |
> kfree(dev); |
> |
> | do_reset
> | //use
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Zheng Wang <zyytlz.wz@163.com>
> ---
> drivers/net/ethernet/xircom/xirc2ps_cs.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/xircom/xirc2ps_cs.c b/drivers/net/ethernet/xircom/xirc2ps_cs.c
> index 894e92ef415b..ea7b06f75691 100644
> --- a/drivers/net/ethernet/xircom/xirc2ps_cs.c
> +++ b/drivers/net/ethernet/xircom/xirc2ps_cs.c
> @@ -503,7 +503,10 @@ static void
> xirc2ps_detach(struct pcmcia_device *link)
> {
> struct net_device *dev = link->priv;
> -
> + struct local_info *local;
> +
> + local = netdev_priv(dev);
> + cancel_work_sync(&local->tx_timeout_task)
> dev_dbg(&link->dev, "detach\n");
>
> unregister_netdev(dev);
This doesn't compile.
Also, the indentation is incorrect.
I think what should have been posted is:
diff --git a/drivers/net/ethernet/xircom/xirc2ps_cs.c b/drivers/net/ethernet/xircom/xirc2ps_cs.c
index 894e92ef415b..b607fea486ab 100644
--- a/drivers/net/ethernet/xircom/xirc2ps_cs.c
+++ b/drivers/net/ethernet/xircom/xirc2ps_cs.c
@@ -503,7 +503,10 @@ static void
xirc2ps_detach(struct pcmcia_device *link)
{
struct net_device *dev = link->priv;
+ struct local_info *local;
+ local = netdev_priv(dev);
+ cancel_work_sync(&local->tx_timeout_task);
dev_dbg(&link->dev, "detach\n");
unregister_netdev(dev);
next prev parent reply other threads:[~2023-03-10 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 16:57 [PATCH net] xirc2ps_cs: Fix use after free bug in xirc2ps_detach Zheng Wang
2023-03-10 13:58 ` Simon Horman [this message]
2023-03-10 16:51 ` Zheng Hacker
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=ZAs3nOoT0GmsLfGN@corigine.com \
--to=simon.horman@corigine.com \
--cc=1395428693sheep@gmail.com \
--cc=alex000young@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hackerzheng666@gmail.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=shayagr@amazon.com \
--cc=thomas.lendacky@amd.com \
--cc=wsa+renesas@sang-engineering.com \
--cc=zyytlz.wz@163.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).