All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Harald Welte <laforge@netfilter.org>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: [BUG] Netfilter ipt_owner deadlock
Date: Mon, 17 May 2004 23:55:39 +0200	[thread overview]
Message-ID: <40A934DB.8070202@trash.net> (raw)
In-Reply-To: <20040517070258.GD26147@obroa-skai.de.gnumonks.org>

Unfortunately I also can't think of a solution except
for marking it broken on SMP ;(

Regards
Patrick

Harald Welte wrote:
> 
> ------------------------------------------------------------------------
> 
> Subject:
> [BUG] Netfilter ipt_owner deadlock
> From:
> Christophe Saout <christophe@saout.de>
> Date:
> Fri, 14 May 2004 17:19:05 +0200
> To:
> linux-net@vger.kernel.org
> 
> To:
> linux-net@vger.kernel.org
> 
> 
> Hi,
> 
> there's a nasty problem with the ipt_owner netfilter code:
> 
> It does a spin_lock(&files->file_lock), sometimes from softirq context.
> This can lead to deadlocks on SMP systems. The lock must not be taken
> from softirq context because the rest of the kernel doesn't use
> spin_lock_bh.
> 
> On a UP machine (that had an SMP compiled kernel) the machine repeatedly
> locked up after approx. five minutes. SysRQ shows backtraces like fput
> -> timer interrupt -> softirq -> ipv4 -> netfilter -> ipt_owner -> hang.
> 
> I don't see a clean solution for this (except for changing all the
> spin_locks to spin_lock_bhs which I think is way too aggressive).
> 
> Any ideas?
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2004-05-17 21:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17  7:02 [BUG] Netfilter ipt_owner deadlock Harald Welte
2004-05-17 21:55 ` Patrick McHardy [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=40A934DB.8070202@trash.net \
    --to=kaber@trash.net \
    --cc=laforge@netfilter.org \
    --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.