From: Jason Wang <jasowang@redhat.com>
To: Andreas Hartmann <andihartmann@01019freenet.de>,
Michal Kubecek <mkubecek@suse.cz>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, Willem de Bruijn <willemb@google.com>
Subject: Re: Linux 4.14 - regression: broken tun/tap / bridge network with virtio - bisected
Date: Fri, 8 Dec 2017 23:11:28 +0800 [thread overview]
Message-ID: <4039a442-88f8-9125-ae08-5dd0bc3ad865@redhat.com> (raw)
In-Reply-To: <1705a3cc-4d9f-8fd0-3eed-9f6a145d5055@01019freenet.de>
On 2017年12月08日 21:13, Andreas Hartmann wrote:
> On 12/08/2017 at 01:58 PM Michal Kubecek wrote:
>> On Fri, Dec 08, 2017 at 01:45:38PM +0100, Andreas Hartmann wrote:
>>> On 12/08/2017 at 12:40 PM Michal Kubecek wrote:
>>>> On Fri, Dec 08, 2017 at 11:31:50AM +0100, Andreas Hartmann wrote:
>>>>> When will there be a fix for 4.14? It is clearly a regression. Is
>>>>> it possible / a good idea to just remove the complete patch series
>>>>> "Remove UDP Fragmentation Offload support"?
>>>> I cannot give an exact date but the patch is queued for stable (see
>>>> http://patchwork.ozlabs.org/bundle/davem/stable/?state=* ) so that
>>>> it should land in stable-4.14 in near future (weeks at most).
>>> Which one is it? I couldn't find any patch related to this problem at
>>> first glance.
>> "[net,v2] net: accept UFO datagrams from tuntap and packet" - the
>> subject was mentioned in one of my earlier e-mails (with commit id).
> Oh - I thought this would only work during live migration (which doesn't
> happen here). My error.
>
>
> Thanks,
> regards,
> Andreas
I think you can either wait it to go for stable or test Linus tree which
has already contained the patch.
Thanks
next prev parent reply other threads:[~2017-12-08 15:11 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-26 14:17 Linux 4.14 - regression: broken tun/tap / bridge network with virtio - bisected Andreas Hartmann
2017-11-27 16:46 ` Andreas Hartmann
2017-11-27 16:55 ` Michal Kubecek
2017-11-27 19:09 ` Andreas Hartmann
2017-12-01 10:11 ` Andreas Hartmann
2017-12-03 11:35 ` Andreas Hartmann
2017-12-04 16:28 ` Andreas Hartmann
2017-12-05 3:50 ` Jason Wang
2017-12-05 16:23 ` Andreas Hartmann
2017-12-06 3:08 ` Jason Wang
2017-12-08 7:21 ` Andreas Hartmann
2017-12-08 8:47 ` Michal Kubecek
2017-12-08 10:31 ` Andreas Hartmann
2017-12-08 11:40 ` Michal Kubecek
2017-12-08 12:45 ` Andreas Hartmann
2017-12-08 12:58 ` Michal Kubecek
2017-12-08 13:13 ` Andreas Hartmann
2017-12-08 15:11 ` Jason Wang [this message]
2017-12-08 16:04 ` Willem de Bruijn
2017-12-08 20:11 ` Andreas Hartmann
2017-12-08 20:44 ` Andreas Hartmann
2017-12-11 15:54 ` Andreas Hartmann
2017-12-14 16:31 ` Andreas Hartmann
2017-12-14 22:17 ` Willem de Bruijn
2017-12-14 22:47 ` Willem de Bruijn
2017-12-15 6:05 ` Andreas Hartmann
2017-12-17 22:33 ` Willem de Bruijn
2017-12-18 17:11 ` Andreas Hartmann
2017-12-20 15:56 ` Andreas Hartmann
2017-12-20 22:44 ` Willem de Bruijn
2017-12-21 17:05 ` Andreas Hartmann
2017-12-21 17:11 ` Willem de Bruijn
2017-12-24 16:24 ` Andreas Hartmann
2017-12-24 18:54 ` Willem de Bruijn
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=4039a442-88f8-9125-ae08-5dd0bc3ad865@redhat.com \
--to=jasowang@redhat.com \
--cc=andihartmann@01019freenet.de \
--cc=davem@davemloft.net \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.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).