From: David Miller <davem@davemloft.net>
To: jasowang@redhat.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
mst@redhat.com, richardcochran@gmail.com,
sergei.shtylyov@cogentembedded.com
Subject: Re: [PATCH V2 net-next 2/2] tuntap: orphan frags before trying to set tx timestamp
Date: Thu, 05 Sep 2013 12:47:02 -0400 (EDT) [thread overview]
Message-ID: <20130905.124702.1612563649224221301.davem@davemloft.net> (raw)
In-Reply-To: <1378374840-39130-2-git-send-email-jasowang@redhat.com>
From: Jason Wang <jasowang@redhat.com>
Date: Thu, 5 Sep 2013 17:54:00 +0800
> sock_tx_timestamp() will clear all zerocopy flags of skb which may lead the
> frags never to be orphaned. This will break guest to guest traffic when zerocopy
> is enabled. Fix this by orphaning the frags before trying to set tx time stamp.
>
> The issue were introduced by commit eda297729171fe16bf34fe5b0419dfb69060f623
> (tun: Support software transmit time stamping).
>
> Cc: Richard Cochran <richardcochran@gmail.com>
> Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Acked-by: Richard Cochran <richardcochran@gmail.com>
> Signed-off-by: Jason Wang <jasowang@redhat.com>
Applied.
I also queued both of these patches to -stable.
Thanks.
next prev parent reply other threads:[~2013-09-05 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 9:53 [PATCH V2 net-next 1/2] tuntap: purge socket error queue on detach Jason Wang
2013-09-05 9:54 ` [PATCH V2 net-next 2/2] tuntap: orphan frags before trying to set tx timestamp Jason Wang
2013-09-05 16:47 ` David Miller [this message]
2013-09-05 16:46 ` [PATCH V2 net-next 1/2] tuntap: purge socket error queue on detach David Miller
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=20130905.124702.1612563649224221301.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=sergei.shtylyov@cogentembedded.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).