netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Rolf Neugebauer <rolf.neugebauer@docker.com>,
	netdev@vger.kernel.org, davem@davemloft.net,
	rppt@linux.vnet.ibm.com
Subject: Re: [PATCH] virtio: don't set VIRTIO_NET_HDR_F_DATA_VALID on xmit
Date: Wed, 18 Jan 2017 17:18:08 +0200	[thread overview]
Message-ID: <20170118171726-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <34158479-8d4a-3761-a02e-66c474aca53e@redhat.com>

On Wed, Jan 18, 2017 at 11:54:21AM +0800, Jason Wang wrote:
> 
> 
> On 2017年01月18日 02:27, Michael S. Tsirkin wrote:
> > On Tue, Jan 17, 2017 at 06:13:51PM +0000, Rolf Neugebauer wrote:
> > > This patch part reverts fd2a0437dc33 and e858fae2b0b8 which introduced a
> > > subtle change in how the virtio_net flags are derived from the SKBs
> > > ip_summed field.
> > > 
> > > With the above commits, the flags are set to VIRTIO_NET_HDR_F_DATA_VALID
> > > when ip_summed == CHECKSUM_UNNECESSARY, thus treating it differently to
> > > ip_summed == CHECKSUM_NONE, which should be the same.
> > > 
> > > Further, the virtio spec 1.0 / CS04 explicitly says that
> > > VIRTIO_NET_HDR_F_DATA_VALID must not be set by the driver.
> > > 
> > > Signed-off-by: Rolf Neugebauer <rolf.neugebauer@docker.com>
> > Fixes: fd2a0437dc33 ("virtio_net: introduce virtio_net_hdr_{from,to}_skb")
> > Fixes: e858fae2b0b8 (" virtio_net: use common code for virtio_net_hdr and skb GSO conversion")
> > Acked-by: Michael S. Tsirkin <mst@redhat.com>
> > 
> > Should be backported into stable as well.
> 
> Looks like a side effect is that we will never see this on receive path?

I thought receive path is using virtio_net_hdr_to_skb - isn't it?

> We
> probably need a hint for virtio_net_hdr_from_skb().
> 
> Thanks
> 
> > 
> > 
> > > ---
> > >   include/linux/virtio_net.h | 2 --
> > >   1 file changed, 2 deletions(-)
> > > 
> > > diff --git a/include/linux/virtio_net.h b/include/linux/virtio_net.h
> > > index 66204007d7ac..56436472ccc7 100644
> > > --- a/include/linux/virtio_net.h
> > > +++ b/include/linux/virtio_net.h
> > > @@ -91,8 +91,6 @@ static inline int virtio_net_hdr_from_skb(const struct sk_buff *skb,
> > >   				skb_checksum_start_offset(skb));
> > >   		hdr->csum_offset = __cpu_to_virtio16(little_endian,
> > >   				skb->csum_offset);
> > > -	} else if (skb->ip_summed == CHECKSUM_UNNECESSARY) {
> > > -		hdr->flags = VIRTIO_NET_HDR_F_DATA_VALID;
> > >   	} /* else everything is zero */
> > >   	return 0;
> > > -- 
> > > 2.11.0

  reply	other threads:[~2017-01-18 15:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17 18:13 [PATCH] virtio: don't set VIRTIO_NET_HDR_F_DATA_VALID on xmit Rolf Neugebauer
2017-01-17 18:27 ` Michael S. Tsirkin
2017-01-17 19:08   ` David Miller
2017-01-18  3:54   ` Jason Wang
2017-01-18 15:18     ` Michael S. Tsirkin [this message]
2017-01-19  3:06       ` Jason Wang
2017-01-19 22:30         ` Michael S. Tsirkin
2017-01-20  3:29           ` Jason Wang
2017-01-18 12:07 ` Sergei Shtylyov

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=20170118171726-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=davem@davemloft.net \
    --cc=jasowang@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=rolf.neugebauer@docker.com \
    --cc=rppt@linux.vnet.ibm.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 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).