mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christophe Saout <christophe@saout.de>
To: "Tobias Ringström" <tobias@ringstrom.mine.nu>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	James Morris <jmorris@redhat.com>
Subject: Re: IPsec/crypto kernel panic in 2.6.[456]
Date: Thu, 20 May 2004 12:18:49 +0200	[thread overview]
Message-ID: <1085048328.25149.8.camel@leto.cs.pocnet.net> (raw)
In-Reply-To: <40ABBA0F.5050805@ringstrom.mine.nu>

Am Mi, den 19.05.2004 um 21:48 Uhr +0200 schrieb Tobias Ringström:

> I have not analyzed the code closely, so I cannot say for certain that 
> there is a problem with that specific changeset, and I'm certainly not 
> out to blame anyone, but reverting it at least seems to fix the problem. 
> The panic occurs when I receive more than a little TCP data in an 
> IPsec ESP tunnel.  I'm of course willing to test patches or provide 
> further info if required.

I've been using linux 2.6. IPSec myself for quite some time and never
seen this. Hmm. What kind of tunnel is this? How large are the packets
involved?

Can you send me your .config and tell me what compiler was used, and
perhaps the object files in your kernel crypto/ directory?

> eax: 0030f000   ebx: 00030f00   ecx: 1b24b797   edx: ba4d7f77
> esi: dcf91438   edi: 77d89bb3   ebp: c040fbb0   esp: c040fb5c
                       ^^^^^^^^

What kind of address is this? Something random? The ESP code uses
in-place decryption, so this should point on the stack.

> ds: 007b   es: 007b   ss: 0068
> Process swapper (pid: 0, threadinfo=c040e000 task=c0386a40)
> Stack:
> 77d89bb3 dcf91330 da6e4458 e38c28ed dcf91438 77d89bb3 c040fbf0 77d89bb3
  ^^^^^^^^                                     ^^^^^^^^          ^^^^^^^

Here it is again.



      parent reply	other threads:[~2004-05-21 23:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-19 19:48 Tobias Ringström
2004-05-19 20:22 ` Andy Isaacson
2004-05-20 10:18 ` Christophe Saout [this message]

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=1085048328.25149.8.camel@leto.cs.pocnet.net \
    --to=christophe@saout.de \
    --cc=akpm@osdl.org \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tobias@ringstrom.mine.nu \
    /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®