From: Thomas Gleixner <tglx@linutronix.de>
To: Patrick McHardy <kaber@trash.net>
Cc: Jan Engelhardt <jengelh@medozas.de>,
linux-rt-users@vger.kernel.org,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: 2.6.29-rc bug near nf_conntrack_tuple_taken
Date: Thu, 26 Feb 2009 00:35:20 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.0902260034330.9135@localhost.localdomain> (raw)
In-Reply-To: <49A400D7.1010404@trash.net>
On Tue, 24 Feb 2009, Patrick McHardy wrote:
> This would mean something has used the non-rcu list functions
> when removing a conntrack from the hash. Which I don't see
> happening anywhere. Another possibility would be that the connntrack
> was already confirmed when the tuple got mangled and the list
> got corrupted. The pr_debug in nf_conntrack_alter_reply should
> trigger in that case.
Don't worry, that's a fallout of -rt, which is fixed in 2.6.29-rc6-rt3
already.
Thanks,
tglx
prev parent reply other threads:[~2009-02-25 23:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 23:49 2.6.29-rc bug near nf_conntrack_tuple_taken Jan Engelhardt
2009-02-24 14:14 ` Patrick McHardy
2009-02-25 23:35 ` Thomas Gleixner [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=alpine.LFD.2.00.0902260034330.9135@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=linux-rt-users@vger.kernel.org \
--cc=netfilter-devel@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