public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Valentijn Sessink <linux-kernel-1074509192@mail.v.sessink.nl>
To: James Morris <jmorris@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: hard crash in IPsec
Date: Mon, 19 Jan 2004 15:23:10 +0100	[thread overview]
Message-ID: <20040119142310.GB2991@openoffice.nl> (raw)
In-Reply-To: <Xine.LNX.4.44.0401190835550.32548-100000@thoron.boston.redhat.com>

Hello James,

At Mon, Jan 19, 2004 at 08:36:57AM -0500, James Morris wrote:
> > 2.6.0/IPsec crashes, fully reproducable. Verified with 2.6.1.
> Could you please verify if this still happens with Netfilter and SELinux 
> disabled at compile time?

It crashes as well, same "Fatal exception in interrupt" behaviour.

I disabled NETFILTER and recompiled (the config_security option was off in
the original setup already):
# CONFIG_NETFILTER is not set
# CONFIG_SECURITY is not set

Crash! I made a picture (sorry, no serial connection here) but unfortunately
the cable to my camera is at home, so if you need the information, you'll
have to wait. However, I guess the problem is easily reproducable. I posted
my .config file at http://valentijn.sessink.nl/temp/config-2.6.1-yangtse-isdn
(this being the config with netfilter, the one that's normally running).

The other end is running 2.6.1 as well, config is config-2.6.1-router

Please note that the config file that causes the crash is wrong, so a
documentation item that says "the Linux kernel is programmed to commit
suicide on brain dead IPsec configurations" will do ;-)

Best regards,

Valentijn
-- 
http://www.openoffice.nl/   Open Office - Linux Office Solutions
Valentijn Sessink  valentyn+sessink@nospam.openoffice.nl

  reply	other threads:[~2004-01-19 14:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19 10:48 hard crash in IPsec Valentijn Sessink
2004-01-19 13:36 ` James Morris
2004-01-19 14:23   ` Valentijn Sessink [this message]
2004-01-19 14:25     ` James Morris

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=20040119142310.GB2991@openoffice.nl \
    --to=linux-kernel-1074509192@mail.v.sessink.nl \
    --cc=jmorris@redhat.com \
    --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