> I have already sent the forwarded message, but I found that those
> crashes don't have anything to do with the kernel messages that I'm
> getting.
They are indeed harmless. I've found the place that generates these
warnings... It only happens when received packets get sent to processes
like listen(1) in raw mode: Sometimes they get mangled before the
receiving process gets them, and those warnings show exactly that this is
happening. It seems to be a buglet in the ax25 receive routine. Harmless,
because all that can happen is listen showing a broken frame now or then...
(The data the application or TCP/IP stack gets is correct.)
Here's the relevant quote from dev.c:
* BEWARE!!! Protocol handlers, mangling input packets,
* MUST BE last in hash buckets and checking protocol handlers
* MUST start from promiscous ptype_all chain in net_bh.
* It is true now, do not change it.
* Explantion follows: if protocol handler, mangling packet, will
* be the first on list, it is not able to sense, that packet
* is cloned and should be copied-on-write, so that it will
* change it and subsequent readers will get broken packet.
* --ANK (980803)
I don't quite understand what a protocol handler is supposed to do,
quite frankly I don't understand much of the "new" (as of 2.1.x)
networking code anyway...
Joerg Reuter http://poboxes.com/jreuter/
And I make my way to where the warm scent of soil fills the evening air.
Everything is waiting quietly out there.... (Anne Clark)
PGP signature
