From: David Hill <dhill@redhat.com>
To: Jason Wang <jasowang@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org
Subject: Re: Shutting down a VM with Kernel 4.14 will sometime hang and a reboot is the only way to recover.
Date: Thu, 30 Nov 2017 15:52:34 -0500 [thread overview]
Message-ID: <623df785-b79c-80d1-899f-6fcc10f70e69@redhat.com> (raw)
In-Reply-To: <68b5d4aa-1d48-d9a1-fc47-62ee8d7ad07a@redhat.com>
On 2017-11-29 09:42 PM, Jason Wang wrote:
>
>
> On 2017年11月30日 03:13, David Hill wrote:
>>
>>
>> On 2017-11-29 12:15 AM, Jason Wang wrote:
>>>
>>>
>>> On 2017年11月29日 10:52, Dave Hill wrote:
>>>>>>
>>>>>
>>>>> Thanks. Zerocopy is disabled by several distribution by default.
>>>>> For upstream, the only reason to let it on is to hope more
>>>>> developers can help and fix the issues.
>>>>>
>>>>>
>>>> So I never hit this issue with previous kernel and this issue
>>>> started happening with the v4.14-rc series.
>>>
>>>
>>> Right, this still need to be investigated if it was introduced
>>> recently.
>>>
>>> Looking at git history, the only suspected commit is for 4.14 is
>>>
>>> commit 1e6f74536de08b5e50cf0e37e735911c2cef7c62
>>> Author: Willem de Bruijn <willemb@google.com>
>>> Date: Fri Oct 6 13:22:31 2017 -0400
>>>
>>> vhost_net: do not stall on zerocopy depletion
>>>
>>> Maybe you can try to revert it and see.
>>>
>>> If it does not solve your issue, I suspect there's bug elsewhere
>>> that cause a packet to be held for very long time.
>>>
>>>> I'm using rawhide so perhaps this is why it isn't disabled by
>>>> default but I have to mention it's an update of FC25 up to FC28 and
>>>> it never got disabled.
>>>> Perhaps it should be disabled in Fedora too if it's not the case...
>>>> I'm not sure this is the place to discuss this ... is it?
>>>
>>> Probably not, but I guess Fedora tries to use new technology
>>> aggressively.
>>>
>>> Thanks
>>
>> I can revert that commit in 4.15-rc1 but I can't find it in 4.14.2
>> ... Is there another commit that could affect this ?
>
> My bad, the suspicious is then:
>
> 1f8b977ab32dc5d148f103326e80d9097f1cefb5 ("sock: enable MSG_ZEROCOPY")
> c1d1b437816f0afa99202be3cb650c9d174667bc ("net: convert (struct
> ubuf_info)->refcnt to refcount_t")
>
> Thanks
>
Reverting those two commits breaks kernel compilation:
net/core/dev.c: In function ‘dev_queue_xmit_nit’:
net/core/dev.c:1952:8: error: implicit declaration of function
‘skb_orphan_frags_rx’; did you mean ‘skb_orphan_frags’?
[-Werror=implicit-function-declaration]
if (!skb_orphan_frags_rx(skb2, GFP_ATOMIC))
^~~~~~~~~~~~~~~~~~~
skb_orphan_frags
I changed skb_orphan_frags_rx to skb_orphan_frags and it compiled but
will everything blow up?
Thanks,
Dave
next prev parent reply other threads:[~2017-11-30 20:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <efd45fba-5724-0036-8473-0274b5816ae9@redhat.com>
2017-11-13 15:54 ` Shutting down a VM with Kernel 4.14 will sometime hang and a reboot is the only way to recover. [1] David Hill
[not found] ` <CALapVYHmf7gG25nA-5LkoaTDR8gB0xQ1Ro_FyyCQNbzrfSp+aQ@mail.gmail.com>
2017-11-15 21:08 ` David Hill
2017-11-22 18:22 ` Shutting down a VM with Kernel 4.14 will sometime hang and a reboot is the only way to recover David Hill
2017-11-23 23:48 ` Paolo Bonzini
2017-11-24 3:11 ` Jason Wang
2017-11-24 16:19 ` David Hill
2017-11-24 16:22 ` David Hill
2017-11-27 3:44 ` Jason Wang
2017-11-27 19:38 ` David Hill
2017-11-28 18:00 ` David Hill
2017-11-29 1:52 ` Jason Wang
2017-11-29 2:52 ` Dave Hill
2017-11-29 5:15 ` Jason Wang
2017-11-29 19:13 ` David Hill
2017-11-30 2:42 ` Jason Wang
2017-11-30 20:52 ` David Hill [this message]
2017-11-30 20:59 ` David Hill
2017-12-01 16:38 ` David Hill
2017-12-04 4:08 ` Jason Wang
2017-12-04 19:51 ` David Hill
2017-12-07 4:34 ` David Hill
2017-12-07 4:42 ` David Hill
2017-12-07 5:13 ` Jason Wang
2017-12-08 18:03 ` David Hill
2017-12-12 3:53 ` David Hill
2017-12-19 3:36 ` Jason Wang
2017-12-19 16:19 ` Willem de Bruijn
2017-12-07 5:12 ` Jason Wang
2017-12-02 16:37 ` Harald Moeller
2017-12-07 2:44 ` David Hill
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=623df785-b79c-80d1-899f-6fcc10f70e69@redhat.com \
--to=dhill@redhat.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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).