public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin F. Knotzke" <shampoo@cam.org>
To: linux-kernel@vger.kernel.org
Subject: protocol fe11 is buggy, dev eth0
Date: Mon, 12 Feb 2001 10:10:56 -0500	[thread overview]
Message-ID: <3A87FD00.1040309@cam.org> (raw)

	Hi,

	I am running kernel 2.2.17 and my logs are littered with:

"protocol fe11 is buggy, dev eth0." I managed to locate where in the 
source code this line gets printed. However I can't say much more then that.

	Any ideas if this has been fixed? Please cc to my address since I am not 
on the list.

	Justin.



This msg comes from the kernel (as syslog mentions), more precisely from
$(LK_SRC_ROOT)/net/core/dev.c (usually $(LK_SRC_ROOT)=/usr/src/linux) :

       /* More sensible variant. 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;
               if (dev->hard_header)
                       skb2->nh.raw += dev->hard_header_len;
       }

-- 
Justin F. Knotzke
shampoo@cam.org
pgp public key http://www.shampoo.ca/pubkey.html

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://vger.kernel.org/lkml/

                 reply	other threads:[~2001-02-12 15:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3A87FD00.1040309@cam.org \
    --to=shampoo@cam.org \
    --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