From: Marcus Sundberg <marcus@ingate.com>
To: Junio C Hamano <junkio@cox.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: PPPoE Oops with 2.4.22-rc
Date: 22 Aug 2003 23:12:56 +0200 [thread overview]
Message-ID: <vebruhz99j.fsf@inigo.ingate.se> (raw)
In-Reply-To: <7v7k559zu5.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> writes:
> >>>>> "MS" == Marcus Sundberg <marcus@ingate.com> writes:
>
> MS> this patch fixes one crash in pppoe_connect():
>
> --- linux-2.4.21-rc2/drivers/net/pppoe.c~ Wed May 14 00:08:52 2003
> +++ linux-2.4.21-rc2/drivers/net/pppoe.c Wed May 14 00:18:47 2003
> @@ -606,7 +606,8 @@
> /* Delete the old binding */
> delete_item(po->pppoe_pa.sid,po->pppoe_pa.remote);
>
> - dev_put(po->pppoe_dev);
> + if (po->pppoe_dev)
> + dev_put(po->pppoe_dev);
>
> memset(po, 0, sizeof(struct pppox_opt));
> po->sk = sk;
>
> Could you explain when/how pppoe_connect gets called with
> (pppoe_dev == NULL) but with an old binding?
I triggered it by doing 'ifconfig down' on the underlying ethernet
device. It's possible there are other ways to trigger it also. When
I made the fix I just looked at where the oops occured.
//Marcus
--
---------------------------------------+--------------------------
Marcus Sundberg <marcus@ingate.com> | Firewalls with SIP & NAT
Firewall Developer, Ingate Systems AB | http://www.ingate.com/
next prev parent reply other threads:[~2003-08-22 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.fl74mr0.184m51s@ifi.uio.no>
[not found] ` <fa.k5266bj.136mf8l@ifi.uio.no>
2003-08-22 20:55 ` [PATCH] Re: PPPoE Oops with 2.4.22-rc Junio C Hamano
2003-08-22 21:12 ` Marcus Sundberg [this message]
2003-08-25 12:57 ` Greg Stark
2003-08-12 6:42 Gabor Z. Papp
2003-08-12 17:16 ` Marcelo Tosatti
2003-08-12 18:05 ` Gabor Z. Papp
2003-08-22 13:43 ` [PATCH] " Marcus Sundberg
2003-08-22 16:54 ` David S. Miller
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=vebruhz99j.fsf@inigo.ingate.se \
--to=marcus@ingate.com \
--cc=junkio@cox.net \
--cc=linux-kernel@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