From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Rustam Kovhaev <rkovhaev@gmail.com>
To: pbonzini@redhat.com, vkuznets@redhat.com, gustavoars@kernel.org
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] KVM: use struct_size() and flex_array_size() helpers in kvm_io_bus_unregister_dev()
Date: Mon, 21 Sep 2020 12:54:57 +0000 [thread overview]
Message-ID: <20200921125457.E1233218AC@mail.kernel.org> (raw)
In-Reply-To: <20200918120500.954436-1-rkovhaev@gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 6425 bytes --]
Hi
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.8.10, v5.4.66, v4.19.146, v4.14.198, v4.9.236, v4.4.236.
v5.8.10: Build OK!
v5.4.66: Build failed! Errors:
virt/kvm/kvm_main.c:4034:5: error: implicit declaration of function ‘flex_array_size’; did you mean ‘array_size’? [-Werror=implicit-function-declaration]
virt/kvm/kvm_main.c:4034:30: error: ‘range’ undeclared (first use in this function)
virt/kvm/kvm_main.c:4034:5: error: implicit declaration of function ‘flex_array_size’; did you mean ‘array_size’? [-Werror=implicit-function-declaration]
virt/kvm/kvm_main.c:4034:30: error: ‘range’ undeclared (first use in this function)
arch/s390/kvm/../../../virt/kvm/kvm_main.c:4034:5: error: implicit declaration of function 'flex_array_size'; did you mean 'array_size'? [-Werror=implicit-function-declaration]
arch/s390/kvm/../../../virt/kvm/kvm_main.c:4034:30: error: 'range' undeclared (first use in this function)
virt/kvm/kvm_main.c:4034:5: error: implicit declaration of function ‘flex_array_size’; did you mean ‘array_size’? [-Werror=implicit-function-declaration]
virt/kvm/kvm_main.c:4034:30: error: ‘range’ undeclared (first use in this function)
virt/kvm/kvm_main.c:4034:5: error: implicit declaration of function ‘flex_array_size’; did you mean ‘array_size’? [-Werror=implicit-function-declaration]
virt/kvm/kvm_main.c:4034:30: error: ‘range’ undeclared (first use in this function)
arch/s390/kvm/../../../virt/kvm/kvm_main.c:4034:5: error: implicit declaration of function 'flex_array_size'; did you mean 'array_size'? [-Werror=implicit-function-declaration]
arch/s390/kvm/../../../virt/kvm/kvm_main.c:4034:30: error: 'range' undeclared (first use in this function)
virt/kvm/kvm_main.c:4034:5: error: implicit declaration of function ‘flex_array_size’; did you mean ‘array_size’? [-Werror=implicit-function-declaration]
virt/kvm/kvm_main.c:4034:30: error: ‘range’ undeclared (first use in this function)
virt/kvm/kvm_main.c:4034:5: error: implicit declaration of function ‘flex_array_size’; did you mean ‘array_size’? [-Werror=implicit-function-declaration]
virt/kvm/kvm_main.c:4034:30: error: ‘range’ undeclared (first use in this function)
arch/s390/kvm/../../../virt/kvm/kvm_main.c:4034:5: error: implicit declaration of function 'flex_array_size'; did you mean 'array_size'? [-Werror=implicit-function-declaration]
arch/s390/kvm/../../../virt/kvm/kvm_main.c:4034:30: error: 'range' undeclared (first use in this function)
virt/kvm/kvm_main.c:4034:5: error: implicit declaration of function ‘flex_array_size’; did you mean ‘array_size’? [-Werror=implicit-function-declaration]
virt/kvm/kvm_main.c:4034:30: error: ‘range’ undeclared (first use in this function)
virt/kvm/kvm_main.c:4034:5: error: implicit declaration of function ‘flex_array_size’; did you mean ‘array_size’? [-Werror=implicit-function-declaration]
virt/kvm/kvm_main.c:4034:30: error: ‘range’ undeclared (first use in this function)
arch/s390/kvm/../../../virt/kvm/kvm_main.c:4034:5: error: implicit declaration of function 'flex_array_size'; did you mean 'array_size'? [-Werror=implicit-function-declaration]
arch/s390/kvm/../../../virt/kvm/kvm_main.c:4034:30: error: 'range' undeclared (first use in this function)
arch/arm64/kvm/../../../virt/kvm/kvm_main.c:4034:5: error: implicit declaration of function 'flex_array_size'; did you mean 'array_size'? [-Werror=implicit-function-declaration]
arch/arm64/kvm/../../../virt/kvm/kvm_main.c:4034:30: error: 'range' undeclared (first use in this function)
v4.19.146: Failed to apply! Possible dependencies:
0804c849f1df ("kvm/x86 : add coalesced pio support")
360cae313702 ("KVM: PPC: Book3S HV: Nested guest entry via hypercall")
41f4e631daf8 ("KVM: PPC: Book3S HV: Extract PMU save/restore operations as C-callable functions")
89329c0be8bd ("KVM: PPC: Book3S HV: Clear partition table entry on vm teardown")
8e3f5fc1045d ("KVM: PPC: Book3S HV: Framework and hcall stubs for nested virtualization")
90952cd38859 ("kvm: Use struct_size() in kmalloc()")
95a6432ce903 ("KVM: PPC: Book3S HV: Streamlined guest entry/exit path on P9 for radix guests")
9943450b7b88 ("kvm/x86 : add document for coalesced mmio")
aa069a996951 ("KVM: PPC: Book3S HV: Add a VM capability to enable nested virtualization")
b12ce36a43f2 ("kvm: Add memcg accounting to KVM allocations")
df709a296ef7 ("KVM: PPC: Book3S HV: Simplify real-mode interrupt handling")
f7035ce9f1df ("KVM: PPC: Book3S HV: Move interrupt delivery on guest entry to C code")
v4.14.198: Failed to apply! Possible dependencies:
0804c849f1df ("kvm/x86 : add coalesced pio support")
7bf14c28ee77 ("Merge branch 'x86/hyperv' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip")
90952cd38859 ("kvm: Use struct_size() in kmalloc()")
b12ce36a43f2 ("kvm: Add memcg accounting to KVM allocations")
d4c67a7a54f1 ("kvm: use insert sort in kvm_io_bus_register_dev function")
v4.9.236: Failed to apply! Possible dependencies:
0804c849f1df ("kvm/x86 : add coalesced pio support")
4a12f9517728 ("KVM: mark kvm->busses as rcu protected")
7bf14c28ee77 ("Merge branch 'x86/hyperv' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip")
90952cd38859 ("kvm: Use struct_size() in kmalloc()")
b12ce36a43f2 ("kvm: Add memcg accounting to KVM allocations")
d4c67a7a54f1 ("kvm: use insert sort in kvm_io_bus_register_dev function")
v4.4.236: Failed to apply! Possible dependencies:
4a12f9517728 ("KVM: mark kvm->busses as rcu protected")
5c919412fe61 ("kvm/x86: Hyper-V synthetic interrupt controller")
6308630bd3db ("kvm/x86: split ioapic-handled and EOI exit bitmaps")
765eaa0f70ea ("kvm/x86: Hyper-V SynIC message slot pending clearing at SINT ack")
90952cd38859 ("kvm: Use struct_size() in kmalloc()")
d4c67a7a54f1 ("kvm: use insert sort in kvm_io_bus_register_dev function")
d62caabb41f3 ("kvm/x86: per-vcpu apicv deactivation support")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
next prev parent reply other threads:[~2020-09-21 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 12:05 [PATCH] KVM: use struct_size() and flex_array_size() helpers in kvm_io_bus_unregister_dev() Rustam Kovhaev
2020-09-19 0:09 ` Gustavo A. R. Silva
2020-09-22 12:43 ` Paolo Bonzini
2020-09-21 12:54 ` Sasha Levin [this message]
2020-09-30 17:58 ` Gustavo A. R. Silva
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=20200921125457.E1233218AC@mail.kernel.org \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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).