mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Henk de Groot <henk.de.groot@hetnet.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-hams@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: AX25/socket kernel PATCHes
Date: Sun, 30 Dec 2001 00:56:25 +0100	[thread overview]
Message-ID: <5.1.0.14.2.20011230004059.00a2ac90@pop.hetnet.nl> (raw)
In-Reply-To: <E16KNor-00059i-00@the-village.bc.nu>
In-Reply-To: <5.1.0.14.2.20011229174504.00a291b0@pop.hetnet.nl>

Hello Alan,

At 18:02 29-12-01 +0000, Alan Cox wrote:
>If you change
>
>                        if (skb2->nh.raw < skb2->data || skb2->nh.raw >= skb2->...
>                                if (net_ratelimit())
>
>So that it checks
>                        < skb2->data || nh.raw > ..
>
>Let me know if that fixes it. It shouldn't but it would be good to know if

I thought I understood but I'm not so sure anymore. I applied the following patch to dev.c:

--------------------------------------------------------------------------
--- linux/net/core/dev.c.orig   Sun Dec 30 00:31:43 2001
+++ linux/net/core/dev.c        Sun Dec 30 00:33:27 2001
@@ -940,7 +940,7 @@
                         */
                        skb2->mac.raw = skb2->data;
 
-                       if (skb2->nh.raw < skb2->data || skb2->nh.raw > skb2->tail) {
+                       if (skb2->nh.raw < skb2->data || 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;
--------------------------------------------------------------------------

This however gives compilation errors, 'nh' undeclared. So no buggy messages anymore :-)...

It's easy for me to generate these buggy messages (each raw transmission seems to produce them) so if there is anything I can try out I'll be happy to do it.

Kind regards,

Henk.

P.S. I'm using a SuSE flavour of the kernel so I have to use the linux-2.4.16.tar.bz2 kernel with SuSE's suse-2.4.16-7.bz2 patches as there are no SuSE addaptations for the 2.4.17 kernel yet (at least last time I checked, i.e. yesterday).


  parent reply	other threads:[~2001-12-29 23:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-28 16:41 link error in SCC driver Wichert Akkerman
2001-12-28 16:56 ` Dave Jones
2001-12-28 16:59   ` Wichert Akkerman
2001-12-28 17:08     ` Daniel T. Chen
2001-12-28 20:57     ` AX25/socket kernel PATCHes Henk de Groot
2001-12-28 23:09       ` Alan Cox
2001-12-28 23:15         ` Jeroen Vreeken
2001-12-29 17:27       ` Henk de Groot
2001-12-29 18:02         ` Alan Cox
2001-12-29 20:37           ` kuznet
2001-12-29 23:56         ` Henk de Groot [this message]
2001-12-30  2:27           ` Alan Cox
2001-12-30 17:23           ` Henk de Groot
2001-12-30 22:13             ` Henk de Groot
2001-12-30 22:24               ` Sandor Dibuz
2002-01-01 22:32             ` Henk de Groot
2001-12-29 17:29       ` Henk de Groot
2001-12-29  3:39     ` link error in SCC driver Keith Owens

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=5.1.0.14.2.20011230004059.00a2ac90@pop.hetnet.nl \
    --to=henk.de.groot@hetnet.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-hams@vger.kernel.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

all inboxes | Powered by JetHome®