From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Westphal Subject: Re: Linux kernel error stack Date: Sun, 5 Aug 2018 22:02:54 +0200 Message-ID: <20180805200254.56dm374j7bsprwrj@breakpoint.cc> References: <20180805094835.3e2njq2f3plj7njj@breakpoint.cc> <20180805194212.r2vdjqjr44gxqgo5@breakpoint.cc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Florian Westphal , netdev@vger.kernel.org To: Satish Patel Return-path: Received: from Chamillionaire.breakpoint.cc ([146.0.238.67]:35510 "EHLO Chamillionaire.breakpoint.cc" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726680AbeHEWIi (ORCPT ); Sun, 5 Aug 2018 18:08:38 -0400 Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: Satish Patel 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.