From: "David S. Miller" <davem@davemloft.net>
To: Patrick McHardy <kaber@trash.net>
Cc: david+challenge-response@blue-labs.org,
linux-kernel@vger.kernel.org, sri@us.ibm.com,
netfilter-devel@lists.netfilter.org
Subject: Re: iptables OOPS (all recent kernels on x86_64)
Date: Mon, 15 Nov 2004 15:15:25 -0800 [thread overview]
Message-ID: <20041115151525.164cc207.davem@davemloft.net> (raw)
In-Reply-To: <41986353.1020800@trash.net>
On Mon, 15 Nov 2004 09:05:39 +0100
Patrick McHardy <kaber@trash.net> wrote:
> David Ford wrote:
>
> > Up until 2.6.9, when I changed link status after the initial
> > configuration, I would get a kernel OOPS. Now with 2.6.9, I get a
> > crash immediately on boot with network device configuration.
> > Attached is my boot log.
>
> Apparently SCTP corrupted the inetaddr notifier chain by registering
> the same notifier_block for IPv4 and IPv6, so masq_inet_event got a
> struct inet6_ifaddr instead of a struct in_ifaddr. This patch should
> fix it.
Looks good, applied. Thanks Patrick.
I'll apply your 2.4.x backport of this fix as well.
prev parent reply other threads:[~2004-11-15 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 6:29 iptables OOPS (all recent kernels on x86_64) David Ford
2004-11-15 8:05 ` Patrick McHardy
2004-11-15 23:15 ` David S. Miller [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=20041115151525.164cc207.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=david+challenge-response@blue-labs.org \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=sri@us.ibm.com \
/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