From: Sean Christopherson <seanjc@google.com>
To: Pavel Skripkin <paskripkin@gmail.com>
Cc: pbonzini@redhat.com, vkuznets@redhat.com, wanpengli@tencent.com,
kvm@vger.kernel.org
Subject: Re: orphan section warnings while building v5.17-rc1
Date: Wed, 26 Jan 2022 16:58:02 +0000 [thread overview]
Message-ID: <YfF9mqcNVYLVERjl@google.com> (raw)
In-Reply-To: <97ce2686-205b-8c46-fd24-116b094a7265@gmail.com>
On Tue, Jan 25, 2022, Pavel Skripkin wrote:
> Hi kvm developers,
>
> while building newest kernel (0280e3c58f92b2fe0e8fbbdf8d386449168de4a8) with
> mostly random config I met following warnings:
>
> LD .tmp_vmlinux.btf
> ld: warning: orphan section `.fixup' from `arch/x86/kvm/xen.o' being placed
> in section `.fixup'
> BTF .btf.vmlinux.bin.o
> LD .tmp_vmlinux.kallsyms1
> ld: warning: orphan section `.fixup' from `arch/x86/kvm/xen.o' being placed
> in section `.fixup'
> KSYMS .tmp_vmlinux.kallsyms1.S
> AS .tmp_vmlinux.kallsyms1.S
> LD .tmp_vmlinux.kallsyms2
> ld: warning: orphan section `.fixup' from `arch/x86/kvm/xen.o' being placed
> in section `.fixup'
> KSYMS .tmp_vmlinux.kallsyms2.S
> AS .tmp_vmlinux.kallsyms2.S
> LD vmlinux
> ld: warning: orphan section `.fixup' from `arch/x86/kvm/xen.o' being placed
> in section `.fixup'
Yep, xen.c has unnecessary usage of .fixup. I'll get a patch sent.
Thanks!
next parent reply other threads:[~2022-01-26 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <97ce2686-205b-8c46-fd24-116b094a7265@gmail.com>
2022-01-26 16:58 ` Sean Christopherson [this message]
2022-01-26 17:11 ` orphan section warnings while building v5.17-rc1 Paolo Bonzini
2022-01-26 17:24 ` Sean Christopherson
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=YfF9mqcNVYLVERjl@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=paskripkin@gmail.com \
--cc=pbonzini@redhat.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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