❌ FAIL: Test report for kernel 5.6.12-200.fc31 (fedora-31)
Hello jforbes, We ran automated tests on the following kernel build: Kernel package: kernel-5.6.12-200.fc31 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=44378050 The results of these automated tests are provided below. Overall result: FAILED (see details below) Tests: FAILED One or more kernel tests failed: s390x: ❌ LTP ppc64le: ❌ LTP aarch64: ❌ LTP x86_64: ❌ LTP All kernel binaries, config files, and logs are available for download here: https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawarehouse/2020/05/11/563205 Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. For the full detail on our testing procedures, please scroll to the bottom of this message. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' __ Hardware testing We booted each kernel and ran the following tests: aarch64: Host 1: ✅ Boot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ Storage blktests Host 2: ✅ Boot test ❌ LTP ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity ✅ CIFS Connectathon ppc64le: Host 1: ✅ Boot test ❌ LTP ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity ✅ CIFS Connectathon Host 2: ✅ Boot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ Storage blktests Host 3: ✅ Boot test ✅ kdump - sysrq-c s390x: Host 1: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ LTP ⚡⚡⚡ Memory function: memfd_create ⚡⚡⚡ Ethernet drivers sanity ⚡⚡⚡ CIFS Connectathon Host 2: ✅ Boot test ✅ stress: stress-ng ✅ Storage blktests Host 3: ✅ Boot test ✅ kdump - sysrq-c Host 4: ✅ Boot test ❌ LTP ✅ Memory function: memfd_create ✅ Ethernet drivers sanity ✅ CIFS Connectathon x86_64: Host 1: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ✅ Boot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ stress: stress-ng ⚡⚡⚡ Storage blktests Host 2: ✅ Boot test ❌ LTP ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity ✅ CIFS Connectathon Host 3: ✅ Boot test ✅ kdump - sysrq-c Test sources: https://github.com/CKI-project/tests-beaker Pull requests are welcome for new tests or improvements to existing tests! Aborted tests - Tests that didn't complete running successfully are marked with ⚡⚡⚡. If this was caused by an infrastructure issue, we try to mark that explicitly in the report. Waived tests If the test run included waived tests, they are marked with . Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed. Testing timeout --- We aim to provide a report within reasonable timeframe. Tests that haven't finished running yet are marked with ⏱. ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Re: Stepping down as Fedora kernel maintainer
On Mon, May 11, 2020 at 5:11 PM Jeremy Cline wrote: > > Hi folks, > > I'm moving on to other things at Red Hat, so I'm stepping down as a > kernel maintainer. I'm not going very far and I'll still be involved in > Fedora generally, so you'll still see me around (especially for the > next few weeks as we complete the transition to the new kernel work- > flow). I leave you in the very capable hands of Justin, who I'd like to > thank for putting up with me these last few years. > You will be missed. Thanks for your contributions to the Fedora kernel and community over the past few years. I am glad to see that you are staying with Red Hat and will have continued involvement in Fedora. Thanks, Justin ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Re: Building custom kernel from src.rpm fails for kernel 5.7
On Mon, 11 May 2020 09:44:54 -0700 stan wrote: > On Mon, 11 May 2020 11:30:26 -0500 > Justin Forbes wrote: > > > when building the kernel with multiple threads, it is entirely > > possible that the failure happens in one thread, but the remaining > > threads make noise while they continue their current task. The error > > can end up a good bit higher in the build log. It is best to look > > through the entire log. The current 5.7 kernels do have some > > changes to support GCC 10, but they should continue to build fine > > on F31 as well, and the ELN builds of these kernels are doing > > headers and tools as well, so the spec should be working with that > > now. > > Thank you, I'll look into that. This is the actual error. arch/x86/kernel/setup.c: In function 'rh_check_supported': arch/x86/kernel/setup.c:824:11: error: 'x86_hyper_type' undeclared (first use in this function); did you mean 'x86_hyper_init'? 824 | guest = (x86_hyper_type != X86_HYPER_NATIVE || boot_cpu_has(X86_FEATURE_HYPERVISOR)); | ^~ | x86_hyper_init arch/x86/kernel/setup.c:824:11: note: each undeclared identifier is reported only once for each function it appears in At top level: arch/x86/kernel/setup.c:820:13: warning: 'rh_check_supported' defined but not used [-Wunused-function] 820 | static void rh_check_supported(void) | ^~ make[2]: *** [scripts/Makefile.build:267: arch/x86/kernel/setup.o] Error 1 make[1]: *** [scripts/Makefile.build:488: arch/x86/kernel] Error 2 make: *** [Makefile:1732: arch/x86] Error 2 make: *** Waiting for unfinished jobs ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Re: Building custom kernel from src.rpm fails for kernel 5.7
On Mon, 11 May 2020 10:52:20 -0400 Prarit Bhargava wrote: > On 5/11/20 10:04 AM, stan wrote: > > Hi, > > > > I build a custom kernel from the src.rpm for the development > > kernels, currently 5.7, on FC31 for x86_64. The 5.6 kernels worked > > just fine, but I can't seem to get 5.7 kernels to build. > Did we turn -Wall on? If yes, that's IMO a mistake to do on the > upstream kernel. I turn on verbose, so that is probably why the warnings are occurring. ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Re: Building custom kernel from src.rpm fails for kernel 5.7
On Mon, May 11, 2020 at 09:52:43AM -0700, stan wrote: > On Mon, 11 May 2020 09:44:54 -0700 > stan wrote: > > > On Mon, 11 May 2020 11:30:26 -0500 > > Justin Forbes wrote: > > > > > when building the kernel with multiple threads, it is entirely > > > possible that the failure happens in one thread, but the remaining > > > threads make noise while they continue their current task. The error > > > can end up a good bit higher in the build log. It is best to look > > > through the entire log. The current 5.7 kernels do have some > > > changes to support GCC 10, but they should continue to build fine > > > on F31 as well, and the ELN builds of these kernels are doing > > > headers and tools as well, so the spec should be working with that > > > now. > > > > Thank you, I'll look into that. > > This is the actual error. > > arch/x86/kernel/setup.c: In function 'rh_check_supported': > arch/x86/kernel/setup.c:824:11: error: 'x86_hyper_type' undeclared (first use > in this function); did you mean 'x86_hyper_init'? > 824 | guest = (x86_hyper_type != X86_HYPER_NATIVE || > boot_cpu_has(X86_FEATURE_HYPERVISOR)); > | ^~ > | x86_hyper_init > arch/x86/kernel/setup.c:824:11: note: each undeclared identifier is reported > only once for each function it appears in > At top level: > arch/x86/kernel/setup.c:820:13: warning: 'rh_check_supported' defined but not > used [-Wunused-function] > 820 | static void rh_check_supported(void) > | ^~ > make[2]: *** [scripts/Makefile.build:267: arch/x86/kernel/setup.o] Error 1 > make[1]: *** [scripts/Makefile.build:488: arch/x86/kernel] Error 2 > make: *** [Makefile:1732: arch/x86] Error 2 > make: *** Waiting for unfinished jobs Odd, the ELN build didn't fail for that reason. You should able to wrap rh_check_supported() with #ifdef CONFIG_RHEL_DIFFERENCES ... #endif (as I am pretty sure your config has the disabled) OR s/x86_hyper_type != X86_HYPER_NATIVE/!hypervisor_is_type(X86_HYPER_NATIVE)/ More fallout quirks. Thanks for your patience! In theory, an ELN build should have failed, someone noticed it was related to a specific RH patch, we revert it temporarily until it is fixed and then re-apply. Still some kinks. Cheers, Don ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Building custom kernel from src.rpm fails for kernel 5.7
Hi, I build a custom kernel from the src.rpm for the development kernels, currently 5.7, on FC31 for x86_64. The 5.6 kernels worked just fine, but I can't seem to get 5.7 kernels to build. I first got the multiple %files error because I build perf and tools, but the [OS-BUILD PATCH] Fix "multiple %files for package kernel-tools" fixed that. But now I get an rpmbuild error that stops the build, but it doesn't give me any reason. The note occurs above this last stanza without issue, so I don't think it has anything to do with the problem. Can you think of any reason this might be occurring? Could there be a dependency missing in the spec file? Is it the ar command failing? Here is the last little bit of output: ./tools/objtool/objtool orc generate --no-fp --uaccess mm/memcontrol.o if objdump -h mm/memcontrol.o | grep -q __ksymtab; then gcc -E -D__GENKSYMS__ -Wp,-MD,mm/.memcontrol.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/9/include -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE -Werror=implicit-function-declaration -Werror=implicit-int -Wno-format-security -Wno-address-of-packed-member -std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno- format-overflow -Wno-address-of-packed-member -O2 --param=allow-store-data-races=0 -fplugin=./scripts/gcc-plugins/latent_entropy_plugin.so -fplugin=./scripts/gcc-plugins/structleak_plugin.so -fplugin=./scripts/gcc-plugins/randomize_layout_plugin.so -fplugin=./scripts/gcc-plugins/stackleak_plugin.so -DLATENT_ENTROPY_PLUGIN -fplugin-arg-structleak_plugin-verbose -fplugin-arg-structleak_plugin-byref-all -DSTRUCTLEAK_PLUGIN -DRANDSTRUCT_PLUGIN -DSTACKLEAK_PLUGIN -fplugin-arg-stackleak_plugin-track-min-size=100 -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wimplicit-fallthrough -Wno-unused-const-variable -fomit-frame-pointer -fno-var-tracking-assignments -fno-inline-functions-called-once -Wdeclaration-after-statement -Wvla -Wno-pointer-sign -Wno-stringop-truncation -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fmacro-prefix-ma p=./= -Wno-packed-not-aligned-DKBUILD_MODFILE='"mm/memcontrol"' -DKBUILD_BASENAME='"memcontrol"' -DKBUILD_MODNAME='"memcontrol"' mm/memcontrol.c | scripts/genksyms/genksyms-r /dev/null > mm/.tmp_memcontrol.ver; ld -m elf_x86_64 -z max-page-size=0x20 -r -o mm/.tmp_memcontrol.o mm/memcontrol.o -T mm/.tmp_memcontrol.ver; mv -f mm/.tmp_memcontrol.o mm/memcontrol.o; rm -f mm/.tmp_memcontrol.ver; fi rm -f mm/built-in.a; ar cDPrST mm/built-in.a mm/filemap.o mm/mempool.o mm/oom_kill.o mm/fadvise.o mm/maccess.o mm/page-writeback.o mm/readahead.o mm/swap.o mm/truncate.o mm/vmscan.o mm/shmem.o mm/util.o mm/mmzone.o mm/vmstat.o mm/backing-dev.o mm/mm_init.o mm/mmu_context.o mm/percpu.o mm/slab_common.o mm/compaction.o mm/vmacache.o mm/interval_tree.o mm/list_lru.o mm/workingset.o mm/debug.o mm/gup.o mm/highmem.o mm/memory.o mm/mincore.o mm/mlock.o mm/mmap.o mm/mmu_gather.o mm/mprotect.o mm/mremap.o mm/msync.o mm/page_vma_mapped.o mm/pagewalk.o mm/pgtable-generic.o mm/rmap.o mm/vmalloc.o mm/process_vm_access.o mm/page_alloc.o mm/shuffle.o mm/init-mm.o mm/memblock.o mm/madvise.o mm/page_io.o mm/swap_state.o mm/swapfile.o mm/swap_slots.o mm/frontswap.o mm/zswap.o mm/dmapool.o mm/hugetlb.o mm/mempolicy.o mm/sparse.o mm/sparse-vmemmap.o mm/mmu_notifier.o mm/ksm.o mm/slub.o mm/migrate.o mm/huge_memory.o mm/khugepaged.o mm/page_counter.o mm/memcontrol.o mm/vmpressure.o mm/swap_cgroup.o mm/ memory-failure.o mm/rodata_test.o mm/cleancache.o mm/page_isolation.o mm/zpool.o mm/zbud.o mm/zsmalloc.o mm/early_ioremap.o mm/memfd.o mm/ptdump.o RPM build errors: And here is the last little bit of error output: mm/memcontrol.c: In function 'mem_cgroup_try_charge_swap': mm/memcontrol.c:7036:23: note: byref variable will be forcibly initialized 7036 | struct page_counter *counter; | ^~~ error: Bad exit status from /var/tmp/rpm-tmp.8rFEzz (%build) Bad exit status from /var/tmp/rpm-tmp.8rFEzz (%build) ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of
Re: Building custom kernel from src.rpm fails for kernel 5.7
On Mon, May 11, 2020 at 9:52 AM Prarit Bhargava wrote: > > On 5/11/20 10:04 AM, stan wrote: > > Hi, > > > > I build a custom kernel from the src.rpm for the development kernels, > > currently 5.7, on FC31 for x86_64. The 5.6 kernels worked just fine, > > but I can't seem to get 5.7 kernels to build. > > > > I first got the multiple %files error because I build perf and tools, > > but the [OS-BUILD PATCH] Fix "multiple %files for package kernel-tools" > > fixed that. But now I get an rpmbuild error that stops the build, but > > it doesn't give me any reason. The note occurs above this last stanza > > without issue, so I don't think it has anything to do with the problem. > > > > Can you think of any reason this might be occurring? Could there be > > a dependency missing in the spec file? Is it the ar command failing? > > > > Here is the last little bit of output: when building the kernel with multiple threads, it is entirely possible that the failure happens in one thread, but the remaining threads make noise while they continue their current task. The error can end up a good bit higher in the build log. It is best to look through the entire log. The current 5.7 kernels do have some changes to support GCC 10, but they should continue to build fine on F31 as well, and the ELN builds of these kernels are doing headers and tools as well, so the spec should be working with that now. ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Re: Building custom kernel from src.rpm fails for kernel 5.7
On 5/11/20 10:04 AM, stan wrote: > Hi, > > I build a custom kernel from the src.rpm for the development kernels, > currently 5.7, on FC31 for x86_64. The 5.6 kernels worked just fine, > but I can't seem to get 5.7 kernels to build. > > I first got the multiple %files error because I build perf and tools, > but the [OS-BUILD PATCH] Fix "multiple %files for package kernel-tools" > fixed that. But now I get an rpmbuild error that stops the build, but > it doesn't give me any reason. The note occurs above this last stanza > without issue, so I don't think it has anything to do with the problem. > > Can you think of any reason this might be occurring? Could there be > a dependency missing in the spec file? Is it the ar command failing? > > Here is the last little bit of output: > >./tools/objtool/objtool orc generate --no-fp --uaccess mm/memcontrol.o > if objdump -h mm/memcontrol.o | grep -q __ksymtab; then gcc -E > -D__GENKSYMS__ -Wp,-MD,mm/.memcontrol.o.d -nostdinc -isystem > /usr/lib/gcc/x86_64-redhat-linux/9/include -I./arch/x86/include > -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi > -I./arch/x86/include/generated/uapi -I./include/uapi > -I./include/generated/uapi -include ./include/linux/kconfig.h -include > ./include/linux/compiler_types.h -D__KERNEL__ -Wall -Wundef > -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common > -fshort-wchar -fno-PIE -Werror=implicit-function-declaration > -Werror=implicit-int -Wno-format-security -Wno-address-of-packed-member > -std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 > -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 > -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone > -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables > -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation > -Wno- > format-overflow -Wno-address-of-packed-member -O2 > --param=allow-store-data-races=0 > -fplugin=./scripts/gcc-plugins/latent_entropy_plugin.so > -fplugin=./scripts/gcc-plugins/structleak_plugin.so > -fplugin=./scripts/gcc-plugins/randomize_layout_plugin.so > -fplugin=./scripts/gcc-plugins/stackleak_plugin.so -DLATENT_ENTROPY_PLUGIN > -fplugin-arg-structleak_plugin-verbose > -fplugin-arg-structleak_plugin-byref-all -DSTRUCTLEAK_PLUGIN > -DRANDSTRUCT_PLUGIN -DSTACKLEAK_PLUGIN > -fplugin-arg-stackleak_plugin-track-min-size=100 -Wframe-larger-than=2048 > -fstack-protector-strong -Wno-unused-but-set-variable -Wimplicit-fallthrough > -Wno-unused-const-variable -fomit-frame-pointer -fno-var-tracking-assignments > -fno-inline-functions-called-once -Wdeclaration-after-statement -Wvla > -Wno-pointer-sign -Wno-stringop-truncation -fno-strict-overflow > -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack > -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init > -fmacro-prefix-ma > p=./= -Wno-packed-not-aligned-DKBUILD_MODFILE='"mm/memcontrol"' > -DKBUILD_BASENAME='"memcontrol"' -DKBUILD_MODNAME='"memcontrol"' > mm/memcontrol.c | scripts/genksyms/genksyms-r /dev/null > > mm/.tmp_memcontrol.ver; ld -m elf_x86_64 -z max-page-size=0x20 -r -o > mm/.tmp_memcontrol.o mm/memcontrol.o -T mm/.tmp_memcontrol.ver; mv -f > mm/.tmp_memcontrol.o mm/memcontrol.o; rm -f mm/.tmp_memcontrol.ver; fi > > > rm -f mm/built-in.a; ar cDPrST mm/built-in.a mm/filemap.o mm/mempool.o > mm/oom_kill.o mm/fadvise.o mm/maccess.o mm/page-writeback.o mm/readahead.o > mm/swap.o mm/truncate.o mm/vmscan.o mm/shmem.o mm/util.o mm/mmzone.o > mm/vmstat.o mm/backing-dev.o mm/mm_init.o mm/mmu_context.o mm/percpu.o > mm/slab_common.o mm/compaction.o mm/vmacache.o mm/interval_tree.o > mm/list_lru.o mm/workingset.o mm/debug.o mm/gup.o mm/highmem.o mm/memory.o > mm/mincore.o mm/mlock.o mm/mmap.o mm/mmu_gather.o mm/mprotect.o mm/mremap.o > mm/msync.o mm/page_vma_mapped.o mm/pagewalk.o mm/pgtable-generic.o mm/rmap.o > mm/vmalloc.o mm/process_vm_access.o mm/page_alloc.o mm/shuffle.o mm/init-mm.o > mm/memblock.o mm/madvise.o mm/page_io.o mm/swap_state.o mm/swapfile.o > mm/swap_slots.o mm/frontswap.o mm/zswap.o mm/dmapool.o mm/hugetlb.o > mm/mempolicy.o mm/sparse.o mm/sparse-vmemmap.o mm/mmu_notifier.o mm/ksm.o > mm/slub.o mm/migrate.o mm/huge_memory.o mm/khugepaged.o mm/page_counter.o > mm/memcontrol.o mm/vmpressure.o mm/swap_cgroup.o mm/ > memory-failure.o mm/rodata_test.o mm/cleancache.o mm/page_isolation.o > mm/zpool.o mm/zbud.o mm/zsmalloc.o mm/early_ioremap.o mm/memfd.o mm/ptdump.o > > > RPM build errors: > > > And here is the last little bit of error output: > > mm/memcontrol.c: In function 'mem_cgroup_try_charge_swap': > mm/memcontrol.c:7036:23: note: byref variable will be forcibly initialized > 7036 | struct page_counter *counter; > | ^~~ > error: Bad exit status from /var/tmp/rpm-tmp.8rFEzz (%build) > Bad exit status from
