From: Patrick McHardy <kaber@trash.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@oss.sgi.com
Subject: Re: [NET] Add missing newline for skb_*_panic
Date: Fri, 22 Apr 2005 02:02:29 +0200 [thread overview]
Message-ID: <42683F15.8000908@trash.net> (raw)
In-Reply-To: <20050421235052.GA10371@gondor.apana.org.au>
Herbert Xu wrote:
> On Fri, Apr 22, 2005 at 01:25:22AM +0200, Patrick McHardy wrote:
>
>>BTW, Do you know if that ppp problem (Fw: [Bugme-new] [Bug 4381] New:
>>When i try to start a pppoe conn., crash at net/core/skbuff.c:91) was
>>already fixed? Otherwise I'd suggest that the reporter should capture
>>a crash again with this patch applied.
>
>
> Unfortunately the reporter says that he can't reproduce it.
>
> However, I have the suspicion that this is really the same as the
> vpnc/tun bug (4279) that prompted you to make the self-modification
> fix to tun.c.
>
> Now there is no doubt that your patch fixed a real bug in tun.c.
> However, I don't think it could have caused the crash in 4279.
> The reason is that the crash dump shows that the length that
> was supplied to skb_put is in fact positive (0xe4 in one case
> and 0xf4 in another).
You're probably right, I only spent a few minutes looking for a
possible reason. Unfortunately the skb_over_panic() output wasn't
included in the report.
> As soon as I get confirmation from the submitter that he can
> still reproduce this I'll get him to try your debugging patch.
Great, thanks.
Regards
Patrick
next prev parent reply other threads:[~2005-04-22 0:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 5:08 [NET] Add missing newline for skb_*_panic Herbert Xu
2005-04-21 22:11 ` Patrick McHardy
2005-04-21 22:20 ` Patrick McHardy
2005-04-21 23:14 ` Herbert Xu
2005-04-21 23:25 ` Patrick McHardy
2005-04-21 23:50 ` Herbert Xu
2005-04-22 0:02 ` Patrick McHardy [this message]
2005-04-21 23:44 ` 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=42683F15.8000908@trash.net \
--to=kaber@trash.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@oss.sgi.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.