All of lore.kernel.org
 help / color / mirror / Atom feed
From: CaT <cat@zip.com.au>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: netfilter oops (Was: Re: Linux 2.4.18-pre2)
Date: Tue, 8 Jan 2002 15:23:49 +1100	[thread overview]
Message-ID: <20020108042348.GB1982@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.21.0201072130170.18722-100000@freak.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0201072130170.18722-100000@freak.distro.conectiva>

On Mon, Jan 07, 2002 at 09:38:17PM -0200, Marcelo Tosatti wrote:
> Here goes pre2.
> 
> 
> pre2: 
*snip*

As I was off the net for 2 weeks I wanted to wait for the next pre
release before reporting this bug (incase I missed something and someone
solved it anyways). Anyhow I'm assuming it still applies to pre2 as
there has been no mention of netfilter changes in the changelog, so...

With 18-pre1, 17-rc2 and 17-preX (can't remember now. It's been a week
or so :/) I can get the kernel to consistantly crash after a few minutes
by compiling it with ipchains compatability and using masqueraded net
connections. If I connect to the getway in quetion without hitting the
masq rules I'm fine. I can also use the net from the gateway, but if I
try to use the net from a box behind it and that box gets masqueraded I
get a kernel lockup and an oops after a minute or so of use. Unfortunately
the oops doesn't actually get recorded anywhere and all I can remember
from it is that it was dieing in 'Swapper task' (or something similar).

I did a bit more experimentation and removed all the netfilter changes
done since 2.4.16 and I no longer got oopses so one of the changes after
2.4.16 broke things.

Unfortunately, I am no longer near said gateway. I -can- try and
duplicate this as soon as I get a version of linux compiling on a debian
woody system.

If you have any questions/requests/whatnots then please yell. If I
succeed in duplicateing this and get a recorded oops I'll send that in
also.

Thanks.

-- 
SOCCER PLAYER IN GENITAL-BITING SCANDAL  ---  "It was something between
friends that I thought would have no importance until this morning when
I got up and saw all  the commotion in the news,"  Gallardo told a news
conference. "It stunned me."
Reyes told Marca that he had "felt a slight pinch."

  reply	other threads:[~2002-01-08  4:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-07 23:38 Linux 2.4.18-pre2 Marcelo Tosatti
2002-01-08  4:23 ` CaT [this message]
2002-01-08 14:04   ` netfilter oops (Was: Re: Linux 2.4.18-pre2) Marcelo Tosatti
2002-01-12  9:56     ` CaT
2002-01-08 21:20 ` Linux 2.4.18-pre2 Rasmus Andersen
  -- strict thread matches above, loose matches on Subject: below --
2002-01-12 11:04 netfilter oops (Was: Re: Linux 2.4.18-pre2) CaT
2002-01-12 12:34 ` CaT
2002-01-12 15:40 Willy Tarreau
2002-01-14  9:59 ` CaT

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=20020108042348.GB1982@zip.com.au \
    --to=cat@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.