From: Wang Chen <wangchen@cn.fujitsu.com>
To: James Chapman <jchapman@katalix.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH -next] ppp: fix segfaults introduced by netdev_priv changes
Date: Fri, 19 Dec 2008 08:42:01 +0800 [thread overview]
Message-ID: <494AEDD9.9060802@cn.fujitsu.com> (raw)
In-Reply-To: <200812181838.mBIIcLlw019317@bert.katalix.com>
James Chapman said the following on 2008-12-19 2:38:
> This patch fixes a segfault in ppp_shutdown_interface() and
> ppp_destroy_interface() when a PPP connection is closed. I bisected
> the problem to the following commit:
>
> commit c8019bf3aff653cceb64f66489fc299ee5957b57
> Author: Wang Chen <wangchen@cn.fujitsu.com>
> Date: Thu Nov 20 04:24:17 2008 -0800
>
> netdevice ppp: Convert directly reference of netdev->priv
>
> 1. Use netdev_priv(dev) to replace dev->priv.
> 2. Alloc netdev's private data by alloc_netdev().
>
> Signed-off-by: Wang Chen <wangchen@cn.fujitsu.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
>
> The original ppp_generic code treated the netdev and struct ppp as
> independent data structures which were freed separately. In moving the
> ppp struct into the netdev, it is now possible for the private data to
> be freed before the call to ppp_shutdown_interface(), which is bad.
>
> The kfree(ppp) in ppp_destroy_interface() is also wrong; presumably
> ppp hasn't worked since the above commit.
>
> The following patch fixes both problems.
>
> Signed-off-by: James Chapman <jchapman@katalix.com>
>
It's ok to me.
Reviewed-by: Wang Chen <wangchen@cn.fujitsu.com>
prev parent reply other threads:[~2008-12-19 0:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 18:38 [PATCH -next] ppp: fix segfaults introduced by netdev_priv changes James Chapman
2008-12-19 0:42 ` Wang Chen [this message]
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=494AEDD9.9060802@cn.fujitsu.com \
--to=wangchen@cn.fujitsu.com \
--cc=davem@davemloft.net \
--cc=jchapman@katalix.com \
--cc=netdev@vger.kernel.org \
/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).