From: Paul Durrant <Paul.Durrant@citrix.com>
To: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: xennet_start_xmit assumptions
Date: Thu, 19 Jan 2017 11:31:14 +0000 [thread overview]
Message-ID: <22c048f35d3845158b225d51dde33bf7@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <20170119111426.GA22018@oracle.com>
> -----Original Message-----
> From: Sowmini Varadhan [mailto:sowmini.varadhan@oracle.com]
> Sent: 19 January 2017 11:14
> To: Paul Durrant <Paul.Durrant@citrix.com>
> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>; Wei Liu
> <wei.liu2@citrix.com>; netdev@vger.kernel.org; xen-
> devel@lists.xenproject.org
> Subject: Re: [Xen-devel] xennet_start_xmit assumptions
>
> On (01/19/17 09:36), Paul Durrant wrote:
> >
> > Hi Sowmini,
> >
> > Sounds like a straightforward bug to me... netfront should be able
> > to handle an empty skb and clearly, if it's relying on skb_headlen()
> > being non-zero, that's not the case.
> >
> > Paul
>
> I see. Seems like there are 2 things broken here: recovering
> from skb->len = 0, and recovering from the more complex
> case of (skb->len > 0 && skb_headlen(skb) == 0)
>
> Do you folks want to take a shot at fixing this,
> since you know the code better? If you are interested,
> I can share my test program to help you reproduce the
> simpler skb->len == 0 case, but it's the fully non-linear
> skbs that may be more interesting to reproduce/fix.
Sowmini,
Yeah, it would be useful to verify any change fixes the particular issue you're seeing so please share the program. For the non-empty non-linear case I'd hope that catching this and doing a pull of some sensible amount of header (which might coincide with the least amount that netback expects to see in the first frag) would be enough.
I can take a shot at a patch for this in the next few days; I'll add your 'Reported-by' so you should get cc-ed.
Cheers,
Paul
>
> I'll probably work on fixing packet_snd to return -EINVAL
> or similar when the len is zero this week.
>
> --Sowmini
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-19 11:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170118153132.GB9258@oracle.com>
2017-01-18 19:25 ` xennet_start_xmit assumptions Konrad Rzeszutek Wilk
[not found] ` <20170118192528.GA6847@char.us.oracle.com>
2017-01-19 9:36 ` Paul Durrant
2017-01-19 11:14 ` Sowmini Varadhan
[not found] ` <20170119111426.GA22018@oracle.com>
2017-01-19 11:31 ` Paul Durrant [this message]
2017-01-19 11:37 ` Sowmini Varadhan
2017-01-19 16:37 ` David Miller
2017-01-19 18:47 ` Sowmini Varadhan
2017-01-19 22:41 ` Sowmini Varadhan
[not found] ` <20170119224123.GB19618@oracle.com>
2017-01-20 19:30 ` David Miller
[not found] ` <20170120.143059.1390682983473502518.davem@davemloft.net>
2017-01-20 20:03 ` Sowmini Varadhan
2017-01-25 15:06 ` Paul Durrant
[not found] ` <fa531e2ed014488baa10556c724e176c@AMSPEX02CL03.citrite.net>
2017-01-25 15:45 ` Sowmini Varadhan
2017-01-18 15:31 Sowmini Varadhan
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=22c048f35d3845158b225d51dde33bf7@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=sowmini.varadhan@oracle.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).