From: Krzysztof Halasa <khc@pm.waw.pl>
To: linux-kernel@vger.kernel.org, dev@able.be, netdev@oss.sgi.com
Subject: Re: Kernel panic using frame relay protocol and IPSec
Date: Fri, 16 Apr 2004 18:10:23 +0200 [thread overview]
Message-ID: <m3ad1b3nv4.fsf@defiant.pm.waw.pl> (raw)
In-Reply-To: <407E93F9.3010105@able.be> (Wim Ceulemans's message of "Thu, 15 Apr 2004 15:54:01 +0200")
Wim Ceulemans <wim.ceulemans@able.be> writes:
> We are using kernel 2.4.24 and super-freeswan 1.99.8.
> When using the frame relay protocol when a psk tunnel is established,
> we are seeing a kernel panic when we ping through the tunnel.
Short version of my email to Wim:
It looks like a known bug - IPSEC code seems to ignore
dev->hard_header_len = 10 requirement for PVC devices and passes skbs
which have less than 10 bytes of header space. Not sure how does it
work with Ethernet which requires 14 bytes, though. It might be a good
idea to investigate.
I wonder if the FR behavior is correct - i.e. is it OK to set
dev->hard_header_len = 10 and expect that all skbs passed to
dev->hard_start_xmit() will have at least 10 bytes of space before
the data?
Does the situation depend on dev->hard_header being non-NULL?
--
Krzysztof Halasa, B*FH
parent reply other threads:[~2004-04-16 16:10 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <407E93F9.3010105@able.be>]
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=m3ad1b3nv4.fsf@defiant.pm.waw.pl \
--to=khc@pm.waw.pl \
--cc=dev@able.be \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).