All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Oester <kernel@linuxace.com>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Deadlocks
Date: Thu, 1 Jul 2004 09:12:04 -0700	[thread overview]
Message-ID: <20040701161204.GA32568@linuxace.com> (raw)
In-Reply-To: <40E28CFA.30206@trash.net>

On Wed, Jun 30, 2004 at 11:50:50AM +0200, Patrick McHardy wrote:
> Could be, but I doubt it. Could you try without CONFIG_NETFILTER_DEBUG
> once more ?

Interestingly, when it crashed that one time it was in tcp_find_option,
and I had a uniprocessor box hang in tcp_find_option yesterday also.  It
looks like I'm hitting the infinite loop discussed here:

http://www.netfilter.org/security/2004-06-30-2.6-tcpoption.html

since I have 2 tcp-option rules:

$IPT -A badtcp -p tcp --tcp-option 64 -j logdrop
$IPT -A badtcp -p tcp --tcp-option 128 -j logdrop

So I'll apply that patch along with your FTP locking patch and see how
it works out.

Phil

      reply	other threads:[~2004-07-01 16:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 18:09 Deadlocks Phil Oester
2004-06-10  8:07 ` Deadlocks Jozsef Kadlecsik
2004-06-10 15:02   ` Deadlocks Phil Oester
2004-06-13 19:58 ` Deadlocks Patrick McHardy
2004-06-15  4:47   ` Deadlocks Phil Oester
2004-06-15  6:23     ` Deadlocks Patrick McHardy
2004-06-17 15:59       ` Deadlocks Phil Oester
2004-06-17 16:20         ` Deadlocks Patrick McHardy
2004-06-18 17:12           ` Deadlocks Phil Oester
2004-06-21  0:46             ` Deadlocks Patrick McHardy
2004-06-22  4:31               ` Deadlocks Phil Oester
2004-06-22  9:52                 ` Deadlocks Patrick McHardy
2004-06-29 17:54               ` Deadlocks Phil Oester
2004-06-29 18:00                 ` Deadlocks Patrick McHardy
2004-06-29 20:09                   ` Deadlocks Phil Oester
2004-06-30  9:50                     ` Deadlocks Patrick McHardy
2004-07-01 16:12                       ` Phil Oester [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=20040701161204.GA32568@linuxace.com \
    --to=kernel@linuxace.com \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.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 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.