Netdev List
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Satish Patel <satish.txt@gmail.com>
Cc: Florian Westphal <fw@strlen.de>, netdev@vger.kernel.org
Subject: Re: Linux kernel error stack
Date: Sun, 5 Aug 2018 22:02:54 +0200	[thread overview]
Message-ID: <20180805200254.56dm374j7bsprwrj@breakpoint.cc> (raw)
In-Reply-To: <CAPgF-fqBFAiUyS=PA9Tcsd0Ga6jdVT6Does7k42Ua43e+LbL9A@mail.gmail.com>

Satish Patel <satish.txt@gmail.com> wrote:
> > [84166:59495417] -A POSTROUTING -p tcp -m tcp --sport 80 -j CHECKSUM
> > --checksum-fill
> > [68739:5153476] -A POSTROUTING -p tcp -m tcp --sport 8000 -j CHECKSUM
> > --checksum-fill

These rules make no sense to me, and are also source of your backtrace.
Who set this up?

If this is coming from openstack, I suggest asking openstack developers
WTH this is supposed to do.

> > [755:275452] -A POSTROUTING -s 10.0.3.0/24 -o lxcbr0 -p udp -m udp
> > --dport 68 -j CHECKSUM --checksum-fill

This was needed to work around dhcpd issues w. checksum offloading but I
guess that DCHCP will work fine without this rule too nowadays.

So I suggest you simply get rid of these rules.

  parent reply	other threads:[~2018-08-05 22:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-05  1:24 Linux kernel error stack Satish Patel
2018-08-05  9:48 ` Florian Westphal
2018-08-05 12:43   ` Satish Patel
2018-08-05 19:42     ` Florian Westphal
2018-08-05 19:54       ` Satish Patel
2018-08-05 19:56         ` Satish Patel
2018-08-05 20:01           ` Satish Patel
2018-08-05 20:02           ` Florian Westphal [this message]
2018-08-05 20:09             ` Satish Patel
2018-08-05 20:15               ` Satish Patel
2018-08-05 20:39                 ` Satish Patel
2018-08-05 20:53                   ` Satish Patel
2018-08-05 21:01                     ` Florian Westphal
2018-08-05 21:03                 ` Florian Westphal
2018-08-05 23:06                   ` Michal Kubecek
2018-08-05 23:15                     ` Florian Westphal
2018-08-06  0:06                       ` Michal Kubecek
2018-08-06  0:19                         ` Florian Westphal

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=20180805200254.56dm374j7bsprwrj@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=netdev@vger.kernel.org \
    --cc=satish.txt@gmail.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