From: Florian Westphal <fw@strlen.de>
To: nuclearcat@nuclearcat.com
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: 4.6.3 panic on nf_ct_delete (nf_conntrack)
Date: Wed, 13 Jul 2016 22:21:13 +0200 [thread overview]
Message-ID: <20160713202113.GA4198@breakpoint.cc> (raw)
In-Reply-To: <df376f88504cb0f20b20acf42962c16d@nuclearcat.com>
nuclearcat@nuclearcat.com <nuclearcat@nuclearcat.com> wrote:
> Workload: pppoe server, 5k users on ppp interfaces. No actual SNAT/DNAT, but
> using connmark and REDIRECT
>
> [176412.990104] general protection fault: 0000 [#1]
> SMP
I assume that you did not see this before.
What was the last kernel version where you did not run into this?
Might help to narrow things down.
next prev parent reply other threads:[~2016-07-13 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 20:06 4.6.3 panic on nf_ct_delete (nf_conntrack) nuclearcat
2016-07-13 20:21 ` Florian Westphal [this message]
2016-07-13 20:37 ` nuclearcat
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=20160713202113.GA4198@breakpoint.cc \
--to=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=nuclearcat@nuclearcat.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 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.