mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bob Dunlop <bob.dunlop@xyzzy.org.uk>
To: Arnaldo Carvalho de Melo <acme@conectiva.com.br>,
	Krzysztof Halasa <khc@pm.waw.pl>,
	linux-kernel@vger.kernel.org
Subject: Re: [GENERIC HDLC LAYER] Messages of a hdlc device
Date: Tue, 16 Jul 2002 16:48:17 +0100	[thread overview]
Message-ID: <20020716164817.B10878@xyzzy.org.uk> (raw)
In-Reply-To: <20020716135818.GB1231@conectiva.com.br>; from acme@conectiva.com.br on Tue, Jul 16, 2002 at 03:57:52PM +0100

Hi,

On Tue, Jul 16,  Arnaldo Carvalho de Melo wrote:
> Em Tue, Jul 16, 2002 at 03:10:33PM +0200, Krzysztof Halasa escreveu:
> > henrique <henrique@cyclades.com> writes:
> > 
> > > I'm using the generic hdlc layer with PPP protocol against a Lucent MAX6000. 
> > > Everything works OK but there a kernel message bothering me:
> > > 
> > > 	protocol 0008 is buggy, dev hdlc0
> > > 
> > > I get this message nearly once per minute.
> > > 
> > > Do anyone know what is this message about ?
>  
> > Not sure what exactly causes it. I was getting it while running tcpdump
> > on PPP device.
> 
> This is becoming a FAQ... see net/core/dev.c, line 907 on 2.5:
> 
>     /* skb->nh should be correctly
>        set by sender, so that the second statement is
>        just protection against buggy protocols.
>      */
>     skb2->mac.raw = skb2->data;
> 
>     if (skb2->nh.raw < skb2->data || skb2->nh.raw > skb2->tail) {
>             if (net_ratelimit())
>                     printk(KERN_DEBUG "protocol %04x is buggy, dev %s\n",
> 			   skb2->protocol, dev->name);
>             skb2->nh.raw = skb2->data;
>     }

Not exactly a FAQ answer though.  How about:

The error would appear to be benign.  Something in the protocol stack is
not setting one of the header fields correctly and this code has corrected
the fault.

This error is only seen when running network monitoring software such as
tcpdump as that is the only time the particular code path that detects
the error is followed.


Also shouldn't that be:
>                     printk(KERN_DEBUG "protocol %04x is buggy, dev %s\n",
>                          htons(skb2->protocol), dev->name);
-- 
        Bob Dunlop

  parent reply	other threads:[~2002-07-16 15:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-15 14:11 henrique
2002-07-16 12:11 ` henrique
2002-07-16 13:52   ` Krzysztof Halasa
2002-07-16 13:10 ` Krzysztof Halasa
2002-07-16 13:58   ` Arnaldo Carvalho de Melo
2002-07-16 14:06     ` Krzysztof Halasa
2002-07-16 15:48     ` Bob Dunlop [this message]
2002-07-16 10:56       ` Arnaldo Carvalho de Melo
2002-08-30 14:19 pavel

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=20020716164817.B10878@xyzzy.org.uk \
    --to=bob.dunlop@xyzzy.org.uk \
    --cc=acme@conectiva.com.br \
    --cc=khc@pm.waw.pl \
    --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

all inboxes | Powered by JetHome®