All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Durrant <paul.durrant@citrix.com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Lyon <andrew.lyon@gmail.com>,
	Andrew
Subject: Re: network misbehaviour with gplpv and 2.6.30
Date: Tue, 21 Jul 2009 10:35:34 +0100	[thread overview]
Message-ID: <4A658BE6.4010803@citrix.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D016DDD27@trantor>

James Harper wrote:
> With GPLPV under 2.6.30, GPLPV gets the following from the ring:
> 
> ring slot n (first buffer):
>  status (length) = 54 bytes
>  offset = 0
>  flags = NETRXF_extra_info (possibly csum too but not relevant)
> ring slot n + 1 (extra info)
>  gso.size (mss) = 1460
> 
> Because NETRXF_extra_info is not set, that's all I get for that packet.

I assume you mean NETRXF_more_data here? Are you saying that ring slot n 
has only NETRXF_extra_info and *not* NETRXF_more_data?

> In the IP header though, the total length is 1544 (which in itself is a
> little strange), but obviously I'm not getting a full packet, just the
> ETH+IP+TCP header.
> 
> According to Andrew Lyon it works fine in previous versions, so this
> problem only arises on 2.6.30. I don't know if netfront on Linux suffers
> from a similar problem.
> 
> I can't identify any changes that could cause this, but if the problem
> is in netback either the frags count isn't being set correctly, or
> skb->cb (which appears to be used temporarily to hold nr_frags) is
> becoming corrupt (set to 0) somehow, but the window where this could
> occur is very small and I can't see where it could happen.
> 
> Any suggestions as to where to start looking?
> 
> (one nice thing is that I have identified a crash that would occur when
> the IP header lied about its length!)
> 
> Thanks
> 
> James
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel


-- 
===============================
Paul Durrant, Software Engineer

Citrix Systems (R&D) Ltd.
First Floor, Building 101
Cambridge Science Park
Milton Road
Cambridge CB4 0FY
United Kingdom

TEL: x35957 (+44 1223 225957)
===============================

  parent reply	other threads:[~2009-07-21  9:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-18  3:42 network misbehaviour with gplpv and 2.6.30 James Harper
2009-07-18 18:28 ` Andrew Lyon
2009-07-21  9:35 ` Paul Durrant [this message]
2009-07-21 10:05   ` James Harper
2009-07-21 10:13     ` Paul Durrant
2009-07-21 11:09       ` James Harper
2009-07-29  9:48       ` Andrew Lyon
2009-07-21 10:53 ` Nerijus Narmontas
2009-07-21 11:01   ` dom0-cpus problem Pasi Kärkkäinen
2009-07-22 15:18     ` Nerijus Narmontas
2009-07-22 15:21       ` dom0-cpus problem with Xen 3.4.1-rc6 Pasi Kärkkäinen
2009-07-22 16:34         ` Nerijus Narmontas
2009-07-22 16:39           ` [Xen-devel] " Pasi Kärkkäinen
2009-07-22 16:42             ` Nerijus Narmontas
2009-07-22 17:01               ` Pasi Kärkkäinen
2009-07-22 17:08                 ` [Xen-devel] " Pasi Kärkkäinen
2009-07-22 17:55                   ` Keir Fraser
2009-07-22 17:15                 ` Keir Fraser
2009-07-22 17:29                   ` [Xen-devel] " Pasi Kärkkäinen
2009-07-22 17:46                     ` Keir Fraser
2009-07-22 18:03                       ` [Xen-devel] " Pasi Kärkkäinen
2009-07-22 17:30                 ` dom0-cpus problem with Xen 3.4.1-rc6 / HVM domains don't die Pasi Kärkkäinen
2009-07-23 13:56                   ` Re: [Xen-devel] " Pasi Kärkkäinen
2009-07-23  9:39       ` [Xen-devel] dom0-cpus problem George Dunlap
2009-07-23 10:03         ` Pasi Kärkkäinen

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=4A658BE6.4010803@citrix.com \
    --to=paul.durrant@citrix.com \
    --cc=andrew.lyon@gmail.com \
    --cc=james.harper@bendigoit.com.au \
    --cc=xen-devel@lists.xensource.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.