linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: build failure after merge of the hyperv tree
@ 2020-03-31  6:23 Stephen Rothwell
  2020-04-01 17:45 ` Wei Liu
  0 siblings, 1 reply; 18+ messages in thread
From: Stephen Rothwell @ 2020-03-31  6:23 UTC (permalink / raw)
  To: Wei Liu
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Tianyu Lan,
	Michael Kelley

[-- Attachment #1: Type: text/plain, Size: 364 bytes --]

Hi all,

After merging the hyperv tree, today's linux-next build (x86_64
allmodconfig) failed like this:

ERROR: modpost: "panic_on_oops" [drivers/hv/hv_vmbus.ko] undefined!

Caused by commit

  a6a5aa4b0179 ("x86/Hyper-V: Report crash data in die() when panic_on_oops is set")

I have reverted that commit for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 18+ messages in thread

* Re: linux-next: build failure after merge of the hyperv tree
  2020-03-31  6:23 Stephen Rothwell
@ 2020-04-01 17:45 ` Wei Liu
  0 siblings, 0 replies; 18+ messages in thread
From: Wei Liu @ 2020-04-01 17:45 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Wei Liu, Linux Next Mailing List, Linux Kernel Mailing List,
	Tianyu Lan, Michael Kelley

On Tue, Mar 31, 2020 at 05:23:35PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the hyperv tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> ERROR: modpost: "panic_on_oops" [drivers/hv/hv_vmbus.ko] undefined!
> 
> Caused by commit
> 
>   a6a5aa4b0179 ("x86/Hyper-V: Report crash data in die() when panic_on_oops is set")
> 
> I have reverted that commit for today.

I will remove that patch from hyperv-next. I have been busy with other
things on Monday and Tuesday, so sorry for not paying close attention.

Wei.

> 
> -- 
> Cheers,
> Stephen Rothwell



^ permalink raw reply	[flat|nested] 18+ messages in thread

* linux-next: build failure after merge of the hyperv tree
@ 2020-06-02  7:35 Stephen Rothwell
  0 siblings, 0 replies; 18+ messages in thread
From: Stephen Rothwell @ 2020-06-02  7:35 UTC (permalink / raw)
  To: Wei Liu, Paolo Bonzini, KVM
  Cc: Linux Next Mailing List, Linux Kernel Mailing List,
	Michael Kelley, Jon Doron

[-- Attachment #1: Type: text/plain, Size: 1730 bytes --]

Hi all,

After merging the hyperv tree, today's linux-next build (x86_64
allmodconfig) failed like this:

arch/x86/kvm/hyperv.c: In function 'kvm_vcpu_ioctl_get_hv_cpuid':
arch/x86/kvm/hyperv.c:2020:16: error: 'HV_X64_DEBUGGING' undeclared (first use in this function); did you mean 'HV_DEBUGGING'?
 2020 |    ent->ebx |= HV_X64_DEBUGGING;
      |                ^~~~~~~~~~~~~~~~
      |                HV_DEBUGGING
arch/x86/kvm/hyperv.c:2020:16: note: each undeclared identifier is reported only once for each function it appears in

Caused by commit

  c55a844f46f9 ("x86/hyperv: Split hyperv-tlfs.h into arch dependent and independent files")

interacting with commit

  f97f5a56f597 ("x86/kvm/hyper-v: Add support for synthetic debugger interface")

from the kvm tree.

I have applied this patch for today:

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Tue, 2 Jun 2020 17:31:06 +1000
Subject: [PATCH] x86/hyperv: merge fix for HV_X64_DEBUGGING name change

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 arch/x86/kvm/hyperv.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c
index abde638548e0..af9cdb426dd2 100644
--- a/arch/x86/kvm/hyperv.c
+++ b/arch/x86/kvm/hyperv.c
@@ -2017,7 +2017,7 @@ int kvm_vcpu_ioctl_get_hv_cpuid(struct kvm_vcpu *vcpu, struct kvm_cpuid2 *cpuid,
 			ent->edx |= HV_FEATURE_FREQUENCY_MSRS_AVAILABLE;
 			ent->edx |= HV_FEATURE_GUEST_CRASH_MSR_AVAILABLE;
 
-			ent->ebx |= HV_X64_DEBUGGING;
+			ent->ebx |= HV_DEBUGGING;
 			ent->edx |= HV_X64_GUEST_DEBUGGING_AVAILABLE;
 			ent->edx |= HV_FEATURE_DEBUG_MSRS_AVAILABLE;
 
-- 
2.26.2

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply related	[flat|nested] 18+ messages in thread

* linux-next: build failure after merge of the hyperv tree
@ 2023-04-18 17:00 broonie
  2023-04-18 17:06 ` Mark Brown
  0 siblings, 1 reply; 18+ messages in thread
From: broonie @ 2023-04-18 17:00 UTC (permalink / raw)
  To: Tianyu Lan, Saurabh Sengar, Wei Liu, Michael Kelley,
	Borislav Petkov, x86
  Cc: Linux Kernel Mailing List, Linux Next Mailing List

Hi all,

After merging the hyperv tree, today's linux-next build (x86 allmodconfig)
failed like this:

/tmp/next/build/arch/x86/kernel/x86_init.c:36:12: error: static declaration of 'set_rtc_noop' follows non-static declaration
   36 | static int set_rtc_noop(const struct timespec64 *now) { return -EINVAL; }
      |            ^~~~~~~~~~~~
In file included from /tmp/next/build/arch/x86/include/asm/mpspec.h:7,
                 from /tmp/next/build/arch/x86/include/asm/topology.h:38,
                 from /tmp/next/build/include/linux/topology.h:36,
                 from /tmp/next/build/include/linux/gfp.h:8,
                 from /tmp/next/build/include/linux/xarray.h:15,
                 from /tmp/next/build/include/linux/radix-tree.h:21,
                 from /tmp/next/build/include/linux/idr.h:15,
                 from /tmp/next/build/include/linux/kernfs.h:12,
                 from /tmp/next/build/include/linux/sysfs.h:16,
                 from /tmp/next/build/include/linux/kobject.h:20,
                 from /tmp/next/build/include/linux/pci.h:35,
                 from /tmp/next/build/arch/x86/kernel/x86_init.c:9:
/tmp/next/build/arch/x86/include/asm/x86_init.h:333:12: note: previous declaration of 'set_rtc_noop' with type 'int(const struct timespec64 *)'
  333 | extern int set_rtc_noop(const struct timespec64 *now);
      |            ^~~~~~~~~~~~
/tmp/next/build/arch/x86/kernel/x86_init.c:37:13: error: static declaration of 'get_rtc_noop' follows non-static declaration
   37 | static void get_rtc_noop(struct timespec64 *now) { }
      |             ^~~~~~~~~~~~
In file included from /tmp/next/build/arch/x86/include/asm/mpspec.h:7,
                 from /tmp/next/build/arch/x86/include/asm/topology.h:38,
                 from /tmp/next/build/include/linux/topology.h:36,
                 from /tmp/next/build/include/linux/gfp.h:8,
                 from /tmp/next/build/include/linux/xarray.h:15,
                 from /tmp/next/build/include/linux/radix-tree.h:21,
                 from /tmp/next/build/include/linux/idr.h:15,
                 from /tmp/next/build/include/linux/kernfs.h:12,
                 from /tmp/next/build/include/linux/sysfs.h:16,
                 from /tmp/next/build/include/linux/kobject.h:20,
                 from /tmp/next/build/include/linux/pci.h:35,
                 from /tmp/next/build/arch/x86/kernel/x86_init.c:9:
/tmp/next/build/arch/x86/include/asm/x86_init.h:334:13: note: previous declaration of 'get_rtc_noop' with type 'void(struct timespec64 *)'
  334 | extern void get_rtc_noop(struct timespec64 *now);
      |             ^~~~~~~~~~~~

Caused by commit

  25dcc7316ef7def25c ("x86/init: Make get/set_rtc_noop() public")

I will use the hyperv tree from yesterday instead.

^ permalink raw reply	[flat|nested] 18+ messages in thread

* Re: linux-next: build failure after merge of the hyperv tree
  2023-04-18 17:00 broonie
@ 2023-04-18 17:06 ` Mark Brown
  2023-04-18 17:24   ` Wei Liu
  0 siblings, 1 reply; 18+ messages in thread
From: Mark Brown @ 2023-04-18 17:06 UTC (permalink / raw)
  To: Tianyu Lan, Saurabh Sengar, Wei Liu, Michael Kelley,
	Borislav Petkov, x86
  Cc: Linux Kernel Mailing List, Linux Next Mailing List, linux-hyperv,
	K. Y. Srinivasan, Haiyang Zhang, Dexuan Cui

[-- Attachment #1: Type: text/plain, Size: 3057 bytes --]

On Tue, Apr 18, 2023 at 06:00:21PM +0100, broonie@kernel.org wrote:
> Hi all,
> 
> After merging the hyperv tree, today's linux-next build (x86 allmodconfig)
> failed like this:

Adding more Hyper-V CCs, sorry the capitialisation in MAINTAINERS
confused my search.

> 
> /tmp/next/build/arch/x86/kernel/x86_init.c:36:12: error: static declaration of 'set_rtc_noop' follows non-static declaration
>    36 | static int set_rtc_noop(const struct timespec64 *now) { return -EINVAL; }
>       |            ^~~~~~~~~~~~
> In file included from /tmp/next/build/arch/x86/include/asm/mpspec.h:7,
>                  from /tmp/next/build/arch/x86/include/asm/topology.h:38,
>                  from /tmp/next/build/include/linux/topology.h:36,
>                  from /tmp/next/build/include/linux/gfp.h:8,
>                  from /tmp/next/build/include/linux/xarray.h:15,
>                  from /tmp/next/build/include/linux/radix-tree.h:21,
>                  from /tmp/next/build/include/linux/idr.h:15,
>                  from /tmp/next/build/include/linux/kernfs.h:12,
>                  from /tmp/next/build/include/linux/sysfs.h:16,
>                  from /tmp/next/build/include/linux/kobject.h:20,
>                  from /tmp/next/build/include/linux/pci.h:35,
>                  from /tmp/next/build/arch/x86/kernel/x86_init.c:9:
> /tmp/next/build/arch/x86/include/asm/x86_init.h:333:12: note: previous declaration of 'set_rtc_noop' with type 'int(const struct timespec64 *)'
>   333 | extern int set_rtc_noop(const struct timespec64 *now);
>       |            ^~~~~~~~~~~~
> /tmp/next/build/arch/x86/kernel/x86_init.c:37:13: error: static declaration of 'get_rtc_noop' follows non-static declaration
>    37 | static void get_rtc_noop(struct timespec64 *now) { }
>       |             ^~~~~~~~~~~~
> In file included from /tmp/next/build/arch/x86/include/asm/mpspec.h:7,
>                  from /tmp/next/build/arch/x86/include/asm/topology.h:38,
>                  from /tmp/next/build/include/linux/topology.h:36,
>                  from /tmp/next/build/include/linux/gfp.h:8,
>                  from /tmp/next/build/include/linux/xarray.h:15,
>                  from /tmp/next/build/include/linux/radix-tree.h:21,
>                  from /tmp/next/build/include/linux/idr.h:15,
>                  from /tmp/next/build/include/linux/kernfs.h:12,
>                  from /tmp/next/build/include/linux/sysfs.h:16,
>                  from /tmp/next/build/include/linux/kobject.h:20,
>                  from /tmp/next/build/include/linux/pci.h:35,
>                  from /tmp/next/build/arch/x86/kernel/x86_init.c:9:
> /tmp/next/build/arch/x86/include/asm/x86_init.h:334:13: note: previous declaration of 'get_rtc_noop' with type 'void(struct timespec64 *)'
>   334 | extern void get_rtc_noop(struct timespec64 *now);
>       |             ^~~~~~~~~~~~
> 
> Caused by commit
> 
>   25dcc7316ef7def25c ("x86/init: Make get/set_rtc_noop() public")
> 
> I will use the hyperv tree from yesterday instead.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 18+ messages in thread

* Re: linux-next: build failure after merge of the hyperv tree
  2023-04-18 17:06 ` Mark Brown
@ 2023-04-18 17:24   ` Wei Liu
  0 siblings, 0 replies; 18+ messages in thread
From: Wei Liu @ 2023-04-18 17:24 UTC (permalink / raw)
  To: Mark Brown
  Cc: Tianyu Lan, Saurabh Sengar, Wei Liu, Michael Kelley,
	Borislav Petkov, x86, Linux Kernel Mailing List,
	Linux Next Mailing List, linux-hyperv, K. Y. Srinivasan,
	Haiyang Zhang, Dexuan Cui

On Tue, Apr 18, 2023 at 06:06:58PM +0100, Mark Brown wrote:
> On Tue, Apr 18, 2023 at 06:00:21PM +0100, broonie@kernel.org wrote:
> > Hi all,
> > 
> > After merging the hyperv tree, today's linux-next build (x86 allmodconfig)
> > failed like this:
> 
> Adding more Hyper-V CCs, sorry the capitialisation in MAINTAINERS
> confused my search.

I will fix this. Thanks for the heads up and sorry for the breakage.

Wei.

^ permalink raw reply	[flat|nested] 18+ messages in thread

* linux-next: build failure after merge of the hyperv tree
@ 2023-04-18 17:31 broonie
  2023-04-18 18:34 ` Wei Liu
  0 siblings, 1 reply; 18+ messages in thread
From: broonie @ 2023-04-18 17:31 UTC (permalink / raw)
  To: Long Li, Michael Kelley, Wei Liu, Dexuan Cui, K. Y. Srinivasan,
	Haiyang Zhang
  Cc: Linux Kernel Mailing List, Linux Next Mailing List, linux-hyperv

Hi all,

After merging the hyperv tree, today's linux-next build (x86 allmodconfig)
failed like this:

/tmp/next/build/drivers/hv/connection.c: In function 'vmbus_connect':
/tmp/next/build/drivers/hv/connection.c:228:53: error: implicit
declaration of function 'hv_alloc_hyperv_page'; did you mean 'hv_free_hyperv_page'? [-Werror=implicit-function-declaration]
  228 |         vmbus_connection.monitor_pages[0] = (void *)hv_alloc_hyperv_page();
      |                                                     ^~~~~~~~~~~~~~~~~~~~
      |                                                     hv_free_hyperv_page
/tmp/next/build/drivers/hv/connection.c:228:45: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]
  228 |         vmbus_connection.monitor_pages[0] = (void *)hv_alloc_hyperv_page();
      |                                             ^
/tmp/next/build/drivers/hv/connection.c:229:45: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]
  229 |         vmbus_connection.monitor_pages[1] = (void *)hv_alloc_hyperv_page();
      |                                             ^
cc1: all warnings being treated as errors

Caused by commit

  4dbdcfe1c5db80edca ("Drivers: hv: move panic report code from vmbus to hv early init code")

I will use the hyperv tree from yesterday instead.

^ permalink raw reply	[flat|nested] 18+ messages in thread

* Re: linux-next: build failure after merge of the hyperv tree
  2023-04-18 17:31 broonie
@ 2023-04-18 18:34 ` Wei Liu
  0 siblings, 0 replies; 18+ messages in thread
From: Wei Liu @ 2023-04-18 18:34 UTC (permalink / raw)
  To: broonie
  Cc: Long Li, Michael Kelley, Wei Liu, Dexuan Cui, K. Y. Srinivasan,
	Haiyang Zhang, Linux Kernel Mailing List, Linux Next Mailing List,
	linux-hyperv

On Tue, Apr 18, 2023 at 06:31:57PM +0100, broonie@kernel.org wrote:
> Hi all,
> 
> After merging the hyperv tree, today's linux-next build (x86 allmodconfig)
> failed like this:
> 
> /tmp/next/build/drivers/hv/connection.c: In function 'vmbus_connect':
> /tmp/next/build/drivers/hv/connection.c:228:53: error: implicit
> declaration of function 'hv_alloc_hyperv_page'; did you mean 'hv_free_hyperv_page'? [-Werror=implicit-function-declaration]
>   228 |         vmbus_connection.monitor_pages[0] = (void *)hv_alloc_hyperv_page();
>       |                                                     ^~~~~~~~~~~~~~~~~~~~
>       |                                                     hv_free_hyperv_page
> /tmp/next/build/drivers/hv/connection.c:228:45: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]
>   228 |         vmbus_connection.monitor_pages[0] = (void *)hv_alloc_hyperv_page();
>       |                                             ^
> /tmp/next/build/drivers/hv/connection.c:229:45: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]
>   229 |         vmbus_connection.monitor_pages[1] = (void *)hv_alloc_hyperv_page();
>       |                                             ^
> cc1: all warnings being treated as errors
> 
> Caused by commit
> 
>   4dbdcfe1c5db80edca ("Drivers: hv: move panic report code from vmbus to hv early init code")
> 
> I will use the hyperv tree from yesterday instead.

This has been fixed by removing the problematic commit.

Thanks,
Wei.

^ permalink raw reply	[flat|nested] 18+ messages in thread

* linux-next: build failure after merge of the hyperv tree
@ 2023-08-07  4:22 Stephen Rothwell
  2023-08-07  4:46 ` Wei Liu
  0 siblings, 1 reply; 18+ messages in thread
From: Stephen Rothwell @ 2023-08-07  4:22 UTC (permalink / raw)
  To: Wei Liu; +Cc: Linux Kernel Mailing List, Linux Next Mailing List

[-- Attachment #1: Type: text/plain, Size: 765 bytes --]

Hi all,

After merging the hyperv tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/pci/controller/pci-hyperv.o: warning: objtool: .altinstr_replacement+0x0: weirdly overlapping alternative! 11 != 6
drivers/hv/hv_balloon.o: warning: objtool: .altinstr_replacement+0x0: weirdly overlapping alternative! 11 != 6
drivers/hv/hv_vmbus.o: warning: objtool: .altinstr_replacement+0x3: weirdly overlapping alternative! 10 != 5
vmlinux.o: warning: objtool: .altinstr_replacement+0x633: weirdly overlapping alternative! 11 != 6
incomplete ORC unwind tables in file: vmlinux
Failed to sort kernel tables

I have no idea what caused this.

I have used the hyperv tree from next-20230804 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 18+ messages in thread

* Re: linux-next: build failure after merge of the hyperv tree
  2023-08-07  4:22 Stephen Rothwell
@ 2023-08-07  4:46 ` Wei Liu
  2023-08-08  2:35   ` Dexuan-Linux Cui
  0 siblings, 1 reply; 18+ messages in thread
From: Wei Liu @ 2023-08-07  4:46 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Wei Liu, Linux Kernel Mailing List, Linux Next Mailing List

On Mon, Aug 07, 2023 at 02:22:38PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the hyperv tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/pci/controller/pci-hyperv.o: warning: objtool: .altinstr_replacement+0x0: weirdly overlapping alternative! 11 != 6
> drivers/hv/hv_balloon.o: warning: objtool: .altinstr_replacement+0x0: weirdly overlapping alternative! 11 != 6
> drivers/hv/hv_vmbus.o: warning: objtool: .altinstr_replacement+0x3: weirdly overlapping alternative! 10 != 5
> vmlinux.o: warning: objtool: .altinstr_replacement+0x633: weirdly overlapping alternative! 11 != 6
> incomplete ORC unwind tables in file: vmlinux
> Failed to sort kernel tables
> 
> I have no idea what caused this.
> 

/me scratches head.

> I have used the hyperv tree from next-20230804 for today.

I've reverted that series from my tree. Thanks for the heads up.

Thanks,
Wei.

^ permalink raw reply	[flat|nested] 18+ messages in thread

* Re: linux-next: build failure after merge of the hyperv tree
  2023-08-07  4:46 ` Wei Liu
@ 2023-08-08  2:35   ` Dexuan-Linux Cui
  0 siblings, 0 replies; 18+ messages in thread
From: Dexuan-Linux Cui @ 2023-08-08  2:35 UTC (permalink / raw)
  To: Wei Liu
  Cc: Stephen Rothwell, Linux Kernel Mailing List,
	Linux Next Mailing List, Dexuan Cui, Tianyu.Lan

On Sun, Aug 6, 2023 at 10:39 PM Wei Liu <wei.liu@kernel.org> wrote:
>
> On Mon, Aug 07, 2023 at 02:22:38PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the hyperv tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > drivers/pci/controller/pci-hyperv.o: warning: objtool: .altinstr_replacement+0x0: weirdly overlapping alternative! 11 != 6
> > drivers/hv/hv_balloon.o: warning: objtool: .altinstr_replacement+0x0: weirdly overlapping alternative! 11 != 6
> > drivers/hv/hv_vmbus.o: warning: objtool: .altinstr_replacement+0x3: weirdly overlapping alternative! 10 != 5
> > vmlinux.o: warning: objtool: .altinstr_replacement+0x633: weirdly overlapping alternative! 11 != 6
> > incomplete ORC unwind tables in file: vmlinux
> > Failed to sort kernel tables
> >
> > I have no idea what caused this.

Hi Stephen,
My kernel source was checked out from the Hyper-V tree's hyperv-next
branch last Friday, which had Tianyu's 8 patches.

I'm able to repro the same build failure in a Ubuntu 22.04 VM with
gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4:

I run the below commands:
make mrproper
make allmodconfig
make -j128
make -j128

...
  LD [M]  net/qrtr/qrtr-tun.ko
  LD [M]  net/qrtr/qrtr-mhi.ko
  LD [M]  virt/lib/irqbypass.ko
  LD [M]  arch/x86/video/fbdev.ko
make: *** [Makefile:234: __sub-make] Error 2

make -j128
  DESCEND objtool
  INSTALL libsubcmd_headers
  CALL    scripts/checksyscalls.sh
  CHK     kernel/kheaders_data.tar.xz
  UPD     include/generated/utsversion.h
  CC      init/version-timestamp.o
  LD      .tmp_vmlinux.kallsyms1
  NM      .tmp_vmlinux.kallsyms1.syms
  KSYMS   .tmp_vmlinux.kallsyms1.S
  AS      .tmp_vmlinux.kallsyms1.S
  LD      .tmp_vmlinux.kallsyms2
  NM      .tmp_vmlinux.kallsyms2.syms
  KSYMS   .tmp_vmlinux.kallsyms2.S
  AS      .tmp_vmlinux.kallsyms2.S
  LD      vmlinux
  NM      System.map
  SORTTAB vmlinux
incomplete ORC unwind tables in file: vmlinux
Failed to sort kernel tables
make[2]: *** [scripts/Makefile.vmlinux:36: vmlinux] Error 1
make[2]: *** Deleting file 'vmlinux'
make[1]: *** [/opt/linux-next/Makefile:1250: vmlinux] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:234: __sub-make] Error 2

If I revert Tianyu's patches by "git diff v6.5-rc4 | patch -Rp1",
the build can succeed.

If I apply the the patches, I get the same failure:

drivers/hv/hv_balloon.o: warning: objtool: .altinstr_replacement+0x0:
weirdly overlapping alternative! 11 != 6
...
drivers/pci/controller/pci-hyperv.o: warning: objtool:
.altinstr_replacement+0x0: weirdly overlapping alternative! 11 != 6
...
drivers/hv/hv_vmbus.o: warning: objtool: .altinstr_replacement+0x3:
weirdly overlapping alternative! 10 != 5
...
  AR      built-in.a
  AR      vmlinux.a
  LD      vmlinux.o
vmlinux.o: warning: objtool: .altinstr_replacement+0x633: weirdly
overlapping alternative! 11 != 6
  OBJCOPY modules.builtin.modinfo
  GEN     modules.builtin
  GEN     .vmlinux.objs
  MODPOST Module.symvers
  CC      .vmlinux.export.o
  UPD     include/generated/utsversion.h
  CC      init/version-timestamp.o
  LD      .tmp_vmlinux.kallsyms1
  NM      .tmp_vmlinux.kallsyms1.syms
  KSYMS   .tmp_vmlinux.kallsyms1.S
  AS      .tmp_vmlinux.kallsyms1.S
  LD      .tmp_vmlinux.kallsyms2
  NM      .tmp_vmlinux.kallsyms2.syms
  KSYMS   .tmp_vmlinux.kallsyms2.S
  AS      .tmp_vmlinux.kallsyms2.S
  LD      vmlinux
  NM      System.map
  SORTTAB vmlinux
incomplete ORC unwind tables in file: vmlinux
Failed to sort kernel tables
make[2]: *** [scripts/Makefile.vmlinux:36: vmlinux] Error 1
make[2]: *** Deleting file 'vmlinux'
make[1]: *** [/opt/linux-next/Makefile:1250: vmlinux] Error 2
make[1]: *** Waiting for unfinished jobs....
...
make: *** [Makefile:234: __sub-make] Error 2

It turns out that I already made a fix
https://github.com/dcui/linux/commit/c4db45f6256248435b2a303b264ecbb41320c41d
which can fix the build failure and fix a crash issue (see
https://lwn.net/ml/linux-kernel/SA1PR21MB1335A21D5D037FE88D9CF820BF0EA@SA1PR21MB1335.namprd21.prod.outlook.com/
)

Thanks,
Dexuan

> /me scratches head.
>
> > I have used the hyperv tree from next-20230804 for today.
>
> I've reverted that series from my tree. Thanks for the heads up.
>
> Thanks,
> Wei.

^ permalink raw reply	[flat|nested] 18+ messages in thread

* linux-next: build failure after merge of the hyperv tree
@ 2024-03-12  4:18 Stephen Rothwell
  2024-03-12  5:25 ` Wei Liu
  0 siblings, 1 reply; 18+ messages in thread
From: Stephen Rothwell @ 2024-03-12  4:18 UTC (permalink / raw)
  To: Wei Liu; +Cc: Nuno Das Neves, Linux Kernel Mailing List,
	Linux Next Mailing List

[-- Attachment #1: Type: text/plain, Size: 569 bytes --]

Hi all,

After merging the hyperv tree, today's linux-next build (i386 defconfig)
failed like this:

arch/x86/kernel/cpu/mshyperv.c:355:5: error: no previous prototype for 'hv_get_hypervisor_version' [-Werror=missing-prototypes]
  355 | int hv_get_hypervisor_version(union hv_hypervisor_version_info *info)
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors

Caused by commit

  1634df06ea12 ("mshyperv: Introduce hv_get_hypervisor_version function")

I have reverted that commit for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 18+ messages in thread

* Re: linux-next: build failure after merge of the hyperv tree
  2024-03-12  4:18 linux-next: build failure after merge of the hyperv tree Stephen Rothwell
@ 2024-03-12  5:25 ` Wei Liu
  0 siblings, 0 replies; 18+ messages in thread
From: Wei Liu @ 2024-03-12  5:25 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Wei Liu, Nuno Das Neves, Linux Kernel Mailing List,
	Linux Next Mailing List

On Tue, Mar 12, 2024 at 03:18:07PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the hyperv tree, today's linux-next build (i386 defconfig)
> failed like this:
> 
> arch/x86/kernel/cpu/mshyperv.c:355:5: error: no previous prototype for 'hv_get_hypervisor_version' [-Werror=missing-prototypes]
>   355 | int hv_get_hypervisor_version(union hv_hypervisor_version_info *info)
>       |     ^~~~~~~~~~~~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors

We noticed this as well.  A fix has been sent out. I will update the tree
shortly.

Thanks,
Wei.

> 
> Caused by commit
> 
>   1634df06ea12 ("mshyperv: Introduce hv_get_hypervisor_version function")
> 
> I have reverted that commit for today.
> 
> -- 
> Cheers,
> Stephen Rothwell



^ permalink raw reply	[flat|nested] 18+ messages in thread

* linux-next: build failure after merge of the hyperv tree
@ 2025-02-13  3:28 Stephen Rothwell
  2025-02-13 22:58 ` Nuno Das Neves
  0 siblings, 1 reply; 18+ messages in thread
From: Stephen Rothwell @ 2025-02-13  3:28 UTC (permalink / raw)
  To: Wei Liu; +Cc: Nuno Das Neves, Linux Kernel Mailing List,
	Linux Next Mailing List

[-- Attachment #1: Type: text/plain, Size: 2226 bytes --]

Hi all,

After merging the hyperv tree, today's linux-next build (x86_64
allmodconfig) failed like this:

In file included from include/asm-generic/bug.h:22,
                 from arch/x86/include/asm/bug.h:99,
                 from include/linux/bug.h:5,
                 from arch/x86/include/asm/paravirt.h:19,
                 from arch/x86/include/asm/irqflags.h:80,
                 from include/linux/irqflags.h:18,
                 from include/linux/spinlock.h:59,
                 from include/linux/mmzone.h:8,
                 from include/linux/gfp.h:7,
                 from include/linux/slab.h:16,
                 from include/linux/resource_ext.h:11,
                 from include/linux/acpi.h:13,
                 from drivers/hv/hv_common.c:16:
drivers/hv/hv_common.c: In function 'hv_get_partition_id':
include/linux/kern_levels.h:5:25: error: format '%lx' expects argument of type 'long unsigned int', but argument 2 has type 'int' [-Werror=format=]
    5 | #define KERN_SOH        "\001"          /* ASCII Start Of Header */
      |                         ^~~~~~
include/linux/printk.h:473:25: note: in definition of macro 'printk_index_wrap'
  473 |                 _p_func(_fmt, ##__VA_ARGS__);                           \
      |                         ^~~~
include/linux/printk.h:544:9: note: in expansion of macro 'printk'
  544 |         printk(KERN_ERR pr_fmt(fmt), ##__VA_ARGS__)
      |         ^~~~~~
include/linux/kern_levels.h:11:25: note: in expansion of macro 'KERN_SOH'
   11 | #define KERN_ERR        KERN_SOH "3"    /* error conditions */
      |                         ^~~~~~~~
include/linux/printk.h:544:16: note: in expansion of macro 'KERN_ERR'
  544 |         printk(KERN_ERR pr_fmt(fmt), ##__VA_ARGS__)
      |                ^~~~~~~~
drivers/hv/hv_common.c:304:17: note: in expansion of macro 'pr_err'
  304 |                 pr_err("Hyper-V: failed to get partition ID: %#lx\n",
      |                 ^~~~~~
cc1: all warnings being treated as errors

Caused by commit

  bc57d252ddf0 ("hyperv: Move hv_current_partition_id to arch-generic code")

I have used the hyperv tree from next-20250212.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 18+ messages in thread

* Re: linux-next: build failure after merge of the hyperv tree
  2025-02-13  3:28 Stephen Rothwell
@ 2025-02-13 22:58 ` Nuno Das Neves
  0 siblings, 0 replies; 18+ messages in thread
From: Nuno Das Neves @ 2025-02-13 22:58 UTC (permalink / raw)
  To: Stephen Rothwell, Wei Liu
  Cc: Linux Kernel Mailing List, Linux Next Mailing List

On 2/12/2025 7:28 PM, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the hyperv tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> In file included from include/asm-generic/bug.h:22,
>                  from arch/x86/include/asm/bug.h:99,
>                  from include/linux/bug.h:5,
>                  from arch/x86/include/asm/paravirt.h:19,
>                  from arch/x86/include/asm/irqflags.h:80,
>                  from include/linux/irqflags.h:18,
>                  from include/linux/spinlock.h:59,
>                  from include/linux/mmzone.h:8,
>                  from include/linux/gfp.h:7,
>                  from include/linux/slab.h:16,
>                  from include/linux/resource_ext.h:11,
>                  from include/linux/acpi.h:13,
>                  from drivers/hv/hv_common.c:16:
> drivers/hv/hv_common.c: In function 'hv_get_partition_id':
> include/linux/kern_levels.h:5:25: error: format '%lx' expects argument of type 'long unsigned int', but argument 2 has type 'int' [-Werror=format=]
>     5 | #define KERN_SOH        "\001"          /* ASCII Start Of Header */
>       |                         ^~~~~~
> include/linux/printk.h:473:25: note: in definition of macro 'printk_index_wrap'
>   473 |                 _p_func(_fmt, ##__VA_ARGS__);                           \
>       |                         ^~~~
> include/linux/printk.h:544:9: note: in expansion of macro 'printk'
>   544 |         printk(KERN_ERR pr_fmt(fmt), ##__VA_ARGS__)
>       |         ^~~~~~
> include/linux/kern_levels.h:11:25: note: in expansion of macro 'KERN_SOH'
>    11 | #define KERN_ERR        KERN_SOH "3"    /* error conditions */
>       |                         ^~~~~~~~
> include/linux/printk.h:544:16: note: in expansion of macro 'KERN_ERR'
>   544 |         printk(KERN_ERR pr_fmt(fmt), ##__VA_ARGS__)
>       |                ^~~~~~~~
> drivers/hv/hv_common.c:304:17: note: in expansion of macro 'pr_err'
>   304 |                 pr_err("Hyper-V: failed to get partition ID: %#lx\n",
>       |                 ^~~~~~
> cc1: all warnings being treated as errors
> 
> Caused by commit
> 
>   bc57d252ddf0 ("hyperv: Move hv_current_partition_id to arch-generic code")
> 
> I have used the hyperv tree from next-20250212.
> 

Thanks Stephen, I have sent a fixup patch to Wei.

I also added W=1 to my make command to catch this in future!

Nuno

^ permalink raw reply	[flat|nested] 18+ messages in thread

* linux-next: build failure after merge of the hyperv tree
@ 2025-05-06  7:26 Stephen Rothwell
  0 siblings, 0 replies; 18+ messages in thread
From: Stephen Rothwell @ 2025-05-06  7:26 UTC (permalink / raw)
  To: Wei Liu; +Cc: Roman Kisel, Linux Kernel Mailing List, Linux Next Mailing List

[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]

Hi all,

After merging the hyperv tree, today's linux-next build (x86_64
allmodconfig) failed like this:

arch/x86/kernel/apic/apic_numachip.c:228:43: error: initialization of 'int (*)(u32,  long unsigned int,  unsigned int)' {aka 'int (*)(unsigned int,  long unsigned int,  unsigned int)'} from incompatible pointer type 'int (*)(u32,  long unsigned int)' {aka 'int (*)(unsigned int,  long unsigned int)'} [-Wincompatible-pointer-types]
  228 |         .wakeup_secondary_cpu           = numachip_wakeup_secondary,
      |                                           ^~~~~~~~~~~~~~~~~~~~~~~~~
arch/x86/kernel/apic/apic_numachip.c:228:43: note: (near initialization for 'apic_numachip1.wakeup_secondary_cpu')
arch/x86/kernel/apic/apic_numachip.c:262:43: error: initialization of 'int (*)(u32,  long unsigned int,  unsigned int)' {aka 'int (*)(unsigned int,  long unsigned int,  unsigned int)'} from incompatible pointer type 'int (*)(u32,  long unsigned int)' {aka 'int (*)(unsigned int,  long unsigned int)'} [-Wincompatible-pointer-types]
  262 |         .wakeup_secondary_cpu           = numachip_wakeup_secondary,
      |                                           ^~~~~~~~~~~~~~~~~~~~~~~~~
arch/x86/kernel/apic/apic_numachip.c:262:43: note: (near initialization for 'apic_numachip2.wakeup_secondary_cpu')

Caused by commit

  2d2d4d8bb009 ("arch/x86: Provide the CPU number in the wakeup AP callback")

I have used the hyperv tree from next-20250505 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 18+ messages in thread

* linux-next: build failure after merge of the hyperv tree
@ 2025-10-20  2:31 Stephen Rothwell
  2025-10-20 17:27 ` Wei Liu
  0 siblings, 1 reply; 18+ messages in thread
From: Stephen Rothwell @ 2025-10-20  2:31 UTC (permalink / raw)
  To: Wei Liu; +Cc: Mukesh Rathor, Linux Kernel Mailing List, Linux Next Mailing List

[-- Attachment #1: Type: text/plain, Size: 628 bytes --]

Hi all,

After merging the hyperv tree, today's linux-next build (x86_64
allmodconfig) failed like this:

arch/x86/hyperv/hv_init.c: In function 'hyperv_init':
arch/x86/hyperv/hv_init.c:558:17: error: implicit declaration of function 'hv_root_crash_init' [-Wimplicit-function-declaration]
  558 |                 hv_root_crash_init();
      |                 ^~~~~~~~~~~~~~~~~~

Caused by commit

  60116744be53 ("x86/hyperv: Enable build of hypervisor crashdump collection files")

$ grep CONFIG_MSHV_ROOT .config
$

I have used the hyperv tree from next-20251017 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 18+ messages in thread

* Re: linux-next: build failure after merge of the hyperv tree
  2025-10-20  2:31 Stephen Rothwell
@ 2025-10-20 17:27 ` Wei Liu
  0 siblings, 0 replies; 18+ messages in thread
From: Wei Liu @ 2025-10-20 17:27 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Wei Liu, Mukesh Rathor, Linux Kernel Mailing List,
	Linux Next Mailing List

On Mon, Oct 20, 2025 at 01:31:44PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the hyperv tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> arch/x86/hyperv/hv_init.c: In function 'hyperv_init':
> arch/x86/hyperv/hv_init.c:558:17: error: implicit declaration of function 'hv_root_crash_init' [-Wimplicit-function-declaration]
>   558 |                 hv_root_crash_init();
>       |                 ^~~~~~~~~~~~~~~~~~
> 
> Caused by commit
> 
>   60116744be53 ("x86/hyperv: Enable build of hypervisor crashdump collection files")
> 
> $ grep CONFIG_MSHV_ROOT .config
> $
> 
> I have used the hyperv tree from next-20251017 for today.

Thanks for the report. I will fix it in hyperv-next.

Wei

> 
> -- 
> Cheers,
> Stephen Rothwell



^ permalink raw reply	[flat|nested] 18+ messages in thread

end of thread, other threads:[~2025-10-20 17:27 UTC | newest]

Thread overview: 18+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-03-12  4:18 linux-next: build failure after merge of the hyperv tree Stephen Rothwell
2024-03-12  5:25 ` Wei Liu
  -- strict thread matches above, loose matches on Subject: below --
2025-10-20  2:31 Stephen Rothwell
2025-10-20 17:27 ` Wei Liu
2025-05-06  7:26 Stephen Rothwell
2025-02-13  3:28 Stephen Rothwell
2025-02-13 22:58 ` Nuno Das Neves
2023-08-07  4:22 Stephen Rothwell
2023-08-07  4:46 ` Wei Liu
2023-08-08  2:35   ` Dexuan-Linux Cui
2023-04-18 17:31 broonie
2023-04-18 18:34 ` Wei Liu
2023-04-18 17:00 broonie
2023-04-18 17:06 ` Mark Brown
2023-04-18 17:24   ` Wei Liu
2020-06-02  7:35 Stephen Rothwell
2020-03-31  6:23 Stephen Rothwell
2020-04-01 17:45 ` Wei Liu

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).