From: Nick Pegg <npegg@linode.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Ian Campbell <ian.campbell@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Questions about XSA39
Date: Fri, 01 Mar 2013 07:41:33 -0500 [thread overview]
Message-ID: <5130A1FD.8090102@linode.com> (raw)
In-Reply-To: <1362138769.2109.149.camel@zion.uk.xensource.com>
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
next prev parent reply other threads:[~2013-03-01 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 20:36 Questions about XSA39 Nick Pegg
2013-03-01 11:52 ` Wei Liu
2013-03-01 12:41 ` Nick Pegg [this message]
2013-03-01 12:23 ` Ian Jackson
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=5130A1FD.8090102@linode.com \
--to=npegg@linode.com \
--cc=JBeulich@suse.com \
--cc=ian.campbell@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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.