From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Pegg Subject: Re: Questions about XSA39 Date: Fri, 01 Mar 2013 07:41:33 -0500 Message-ID: <5130A1FD.8090102@linode.com> References: <512FBFBF.7090408@linode.com> <1362138769.2109.149.camel@zion.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1362138769.2109.149.camel@zion.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Wei Liu Cc: Konrad Rzeszutek Wilk , Ian Campbell , Jan Beulich , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 3/1/13 6:52 AM, Wei Liu wrote: > On Thu, 2013-02-28 at 20:36 +0000, Nick Pegg wrote: >> Hi Xen developers, >> >> I had some questions regarding XSA39, and I hope you all can answer them. >> >> We've been rolling out some hosts with the XSA39 patch applied and have >> come across a problem where a few of our customer DomUs keep hitting the >> conditions which call netbk_fatal_tx_err(), mostly "Frag is bigger than > > "mostly" or "all"? As all the reports I've seen so far are "Frag is > bigger than frame", so it would be interesting to know whether there's > any other error as well. > > We're investigating whether this is a genuine bug in Xen netfront / > netback implementation, or it is something in kernel generating bogus > packet. The solution to this issue may different depending on various > factors. > > > Wei. > After digging through our recent logs, we had four occurrences of "Too many frags." All others (>85%) were "Frag is bigger than frame." -Nick