April 2025 - Linux-stable-mirror

[REGRESSION] stable-rc/linux-6.12.y: (build) expected ‘)’ before ‘BPF_INTERNAL’ in .vmlinux.export.o (.vmlinux....

by KernelCI bot

Hello, New build issue found on stable-rc/linux-6.12.y: --- expected ‘)’ before ‘BPF_INTERNAL’ in .vmlinux.export.o (.vmlinux.export.c) [logspec:kbuild,kbuild.compiler.error] --- - dashboard: https://d.kernelci.org/i/maestro:6ffcf98c66c5d150243f133e2b6545c2360d68a8 - giturl: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git - commit HEAD: 0f114e4705bd70a1aade95111161a0a24a597879 Log excerpt: ===================================================== .vmlinux.export.c:1417:33: error: expected ‘)’ before ‘BPF_INTERNAL’ 1417 | KSYMTAB_FUNC(bpf_map_get, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:45:28: note: in definition of macro ‘__KSYMTAB’ 45 | " .asciz \"" ns "\"" "\n" \ | ^~ .vmlinux.export.c:1417:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 1417 | KSYMTAB_FUNC(bpf_map_get, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:41:12: note: to match this ‘(’ 41 | asm(" .section \"__ksymtab_strings\",\"aMS\",%progbits,1" "\n" \ | ^ ./include/linux/export-internal.h:62:41: note: in expansion of macro ‘__KSYMTAB’ 62 | #define KSYMTAB_FUNC(name, sec, ns) __KSYMTAB(name, KSYM_FUNC(name), sec, ns) | ^~~~~~~~~ .vmlinux.export.c:1417:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 1417 | KSYMTAB_FUNC(bpf_map_get, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ .vmlinux.export.c:1426:42: error: expected ‘)’ before ‘BPF_INTERNAL’ 1426 | KSYMTAB_FUNC(bpf_link_get_from_fd, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:45:28: note: in definition of macro ‘__KSYMTAB’ 45 | " .asciz \"" ns "\"" "\n" \ | ^~ .vmlinux.export.c:1426:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 1426 | KSYMTAB_FUNC(bpf_link_get_from_fd, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:41:12: note: to match this ‘(’ 41 | asm(" .section \"__ksymtab_strings\",\"aMS\",%progbits,1" "\n" \ | ^ ./include/linux/export-internal.h:62:41: note: in expansion of macro ‘__KSYMTAB’ 62 | #define KSYMTAB_FUNC(name, sec, ns) __KSYMTAB(name, KSYM_FUNC(name), sec, ns) | ^~~~~~~~~ .vmlinux.export.c:1426:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 1426 | KSYMTAB_FUNC(bpf_link_get_from_fd, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ .vmlinux.export.c:1428:34: error: expected ‘)’ before ‘BPF_INTERNAL’ 1428 | KSYMTAB_FUNC(kern_sys_bpf, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:45:28: note: in definition of macro ‘__KSYMTAB’ 45 | " .asciz \"" ns "\"" "\n" \ | ^~ .vmlinux.export.c:1428:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 1428 | KSYMTAB_FUNC(kern_sys_bpf, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:41:12: note: to match this ‘(’ 41 | asm(" .section \"__ksymtab_strings\",\"aMS\",%progbits,1" "\n" \ | ^ ./include/linux/export-internal.h:62:41: note: in expansion of macro ‘__KSYMTAB’ 62 | #define KSYMTAB_FUNC(name, sec, ns) __KSYMTAB(name, KSYM_FUNC(name), sec, ns) | ^~~~~~~~~ .vmlinux.export.c:1428:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 1428 | KSYMTAB_FUNC(kern_sys_bpf, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ===================================================== # Builds where the incident occurred: ## multi_v7_defconfig+kselftest on (arm): - compiler: gcc-12 - dashboard: https://d.kernelci.org/build/maestro:680fc2ab43948caad95c1595 #kernelci issue maestro:6ffcf98c66c5d150243f133e2b6545c2360d68a8 Reported-by: kernelci.org bot <bot(a)kernelci.org> -- This is an experimental report format. Please send feedback in! Talk to us at kernelci(a)lists.linux.dev Made with love by the KernelCI team - https://kernelci.org

4 months, 1 week

1
0
0 0

[REGRESSION] stable-rc/linux-6.12.y: (build) expected ‘)’ before ‘BPF_INTERNAL’ in .vmlinux.export.o (.vmlinux....

by KernelCI bot

Hello, New build issue found on stable-rc/linux-6.12.y: --- expected ‘)’ before ‘BPF_INTERNAL’ in .vmlinux.export.o (.vmlinux.export.c) [logspec:kbuild,kbuild.compiler.error] --- - dashboard: https://d.kernelci.org/i/maestro:5da0a9a420589f98d3a8ea7cb0afbba8ecc7606d - giturl: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git - commit HEAD: 0f114e4705bd70a1aade95111161a0a24a597879 Log excerpt: ===================================================== .vmlinux.export.c:1260:33: error: expected ‘)’ before ‘BPF_INTERNAL’ 1260 | KSYMTAB_FUNC(bpf_map_get, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:45:28: note: in definition of macro ‘__KSYMTAB’ 45 | " .asciz \"" ns "\"" "\n" \ | ^~ .vmlinux.export.c:1260:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 1260 | KSYMTAB_FUNC(bpf_map_get, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:41:12: note: to match this ‘(’ 41 | asm(" .section \"__ksymtab_strings\",\"aMS\",%progbits,1" "\n" \ | ^ ./include/linux/export-internal.h:62:41: note: in expansion of macro ‘__KSYMTAB’ 62 | #define KSYMTAB_FUNC(name, sec, ns) __KSYMTAB(name, KSYM_FUNC(name), sec, ns) | ^~~~~~~~~ .vmlinux.export.c:1260:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 1260 | KSYMTAB_FUNC(bpf_map_get, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ .vmlinux.export.c:1269:42: error: expected ‘)’ before ‘BPF_INTERNAL’ 1269 | KSYMTAB_FUNC(bpf_link_get_from_fd, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:45:28: note: in definition of macro ‘__KSYMTAB’ 45 | " .asciz \"" ns "\"" "\n" \ | ^~ .vmlinux.export.c:1269:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 1269 | KSYMTAB_FUNC(bpf_link_get_from_fd, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:41:12: note: to match this ‘(’ 41 | asm(" .section \"__ksymtab_strings\",\"aMS\",%progbits,1" "\n" \ | ^ ./include/linux/export-internal.h:62:41: note: in expansion of macro ‘__KSYMTAB’ 62 | #define KSYMTAB_FUNC(name, sec, ns) __KSYMTAB(name, KSYM_FUNC(name), sec, ns) | ^~~~~~~~~ .vmlinux.export.c:1269:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 1269 | KSYMTAB_FUNC(bpf_link_get_from_fd, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ .vmlinux.export.c:1271:34: error: expected ‘)’ before ‘BPF_INTERNAL’ 1271 | KSYMTAB_FUNC(kern_sys_bpf, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:45:28: note: in definition of macro ‘__KSYMTAB’ 45 | " .asciz \"" ns "\"" "\n" \ | ^~ .vmlinux.export.c:1271:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 1271 | KSYMTAB_FUNC(kern_sys_bpf, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:41:12: note: to match this ‘(’ 41 | asm(" .section \"__ksymtab_strings\",\"aMS\",%progbits,1" "\n" \ | ^ ./include/linux/export-internal.h:62:41: note: in expansion of macro ‘__KSYMTAB’ 62 | #define KSYMTAB_FUNC(name, sec, ns) __KSYMTAB(name, KSYM_FUNC(name), sec, ns) | ^~~~~~~~~ .vmlinux.export.c:1271:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 1271 | KSYMTAB_FUNC(kern_sys_bpf, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ===================================================== # Builds where the incident occurred: ## defconfig+arm64-chromebook+kselftest on (arm64): - compiler: gcc-12 - dashboard: https://d.kernelci.org/build/maestro:680fc2cc43948caad95c15b4 ## defconfig+lab-setup+kselftest on (arm64): - compiler: gcc-12 - dashboard: https://d.kernelci.org/build/maestro:680fc2c243948caad95c15aa #kernelci issue maestro:5da0a9a420589f98d3a8ea7cb0afbba8ecc7606d Reported-by: kernelci.org bot <bot(a)kernelci.org> -- This is an experimental report format. Please send feedback in! Talk to us at kernelci(a)lists.linux.dev Made with love by the KernelCI team - https://kernelci.org

4 months, 1 week

1
0
0 0

[REGRESSION] stable-rc/linux-5.15.y: (build) ‘MSM_UART_CR_CMD_RESET_RX’ undeclared (first use in this function)...

by KernelCI bot

Hello, New build issue found on stable-rc/linux-5.15.y: --- ‘MSM_UART_CR_CMD_RESET_RX’ undeclared (first use in this function); did you mean ‘UART_CR_CMD_RESET_RX’? in drivers/tty/serial/msm_serial.o (drivers/tty/serial/msm_serial.c) [logspec:kbuild,kbuild.compiler.error] --- - dashboard: https://d.kernelci.org/i/maestro:8f9e585d814ad41cea3f055c8d011c099a1ac9ad - giturl: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git - commit HEAD: 7e1718e4648c8d93f1738a07033b83f2fd6b43e5 Log excerpt: ===================================================== drivers/tty/serial/msm_serial.c:1737:34: error: ‘MSM_UART_CR_CMD_RESET_RX’ undeclared (first use in this function); did you mean ‘UART_CR_CMD_RESET_RX’? 1737 | msm_write(&device->port, MSM_UART_CR_CMD_RESET_RX, MSM_UART_CR); | ^~~~~~~~~~~~~~~~~~~~~~~~ | UART_CR_CMD_RESET_RX drivers/tty/serial/msm_serial.c:1737:34: note: each undeclared identifier is reported only once for each function it appears in drivers/tty/serial/msm_serial.c:1737:60: error: ‘MSM_UART_CR’ undeclared (first use in this function); did you mean ‘UART_CR’? 1737 | msm_write(&device->port, MSM_UART_CR_CMD_RESET_RX, MSM_UART_CR); | ^~~~~~~~~~~ | UART_CR drivers/tty/serial/msm_serial.c:1738:34: error: ‘MSM_UART_CR_CMD_RESET_TX’ undeclared (first use in this function); did you mean ‘UART_CR_CMD_RESET_TX’? 1738 | msm_write(&device->port, MSM_UART_CR_CMD_RESET_TX, MSM_UART_CR); | ^~~~~~~~~~~~~~~~~~~~~~~~ | UART_CR_CMD_RESET_TX drivers/tty/serial/msm_serial.c:1739:34: error: ‘MSM_UART_CR_TX_ENABLE’ undeclared (first use in this function); did you mean ‘UART_CR_TX_ENABLE’? 1739 | msm_write(&device->port, MSM_UART_CR_TX_ENABLE, MSM_UART_CR); | ^~~~~~~~~~~~~~~~~~~~~ | UART_CR_TX_ENABLE ===================================================== # Builds where the incident occurred: ## defconfig+arm64-chromebook+kselftest on (arm64): - compiler: gcc-12 - dashboard: https://d.kernelci.org/build/maestro:680fc0e643948caad95c107c ## defconfig+lab-setup+arm64-chromebook+CONFIG_MODULE_COMPRESS=n+CONFIG_MODULE_COMPRESS_NONE=y on (arm64): - compiler: gcc-12 - dashboard: https://d.kernelci.org/build/maestro:680fc09343948caad95c0ea0 #kernelci issue maestro:8f9e585d814ad41cea3f055c8d011c099a1ac9ad Reported-by: kernelci.org bot <bot(a)kernelci.org> -- This is an experimental report format. Please send feedback in! Talk to us at kernelci(a)lists.linux.dev Made with love by the KernelCI team - https://kernelci.org

4 months, 1 week

1
0
0 0

[REGRESSION] stable-rc/linux-6.12.y: (build) expected ‘)’ before ‘BPF_INTERNAL’ in .vmlinux.export.o (.vmlinux....

by KernelCI bot

Hello, New build issue found on stable-rc/linux-6.12.y: --- expected ‘)’ before ‘BPF_INTERNAL’ in .vmlinux.export.o (.vmlinux.export.c) [logspec:kbuild,kbuild.compiler.error] --- - dashboard: https://d.kernelci.org/i/maestro:b3bf65712cbf0afb6965b8e30e3b0b32d73bf462 - giturl: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git - commit HEAD: 0f114e4705bd70a1aade95111161a0a24a597879 Log excerpt: ===================================================== .vmlinux.export.c:2011:33: error: expected ‘)’ before ‘BPF_INTERNAL’ 2011 | KSYMTAB_FUNC(bpf_map_get, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:45:28: note: in definition of macro ‘__KSYMTAB’ 45 | " .asciz \"" ns "\"" "\n" \ | ^~ .vmlinux.export.c:2011:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 2011 | KSYMTAB_FUNC(bpf_map_get, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:41:12: note: to match this ‘(’ 41 | asm(" .section \"__ksymtab_strings\",\"aMS\",%progbits,1" "\n" \ | ^ ./include/linux/export-internal.h:62:41: note: in expansion of macro ‘__KSYMTAB’ 62 | #define KSYMTAB_FUNC(name, sec, ns) __KSYMTAB(name, KSYM_FUNC(name), sec, ns) | ^~~~~~~~~ .vmlinux.export.c:2011:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 2011 | KSYMTAB_FUNC(bpf_map_get, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ .vmlinux.export.c:2020:42: error: expected ‘)’ before ‘BPF_INTERNAL’ 2020 | KSYMTAB_FUNC(bpf_link_get_from_fd, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:45:28: note: in definition of macro ‘__KSYMTAB’ 45 | " .asciz \"" ns "\"" "\n" \ | ^~ .vmlinux.export.c:2020:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 2020 | KSYMTAB_FUNC(bpf_link_get_from_fd, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:41:12: note: to match this ‘(’ 41 | asm(" .section \"__ksymtab_strings\",\"aMS\",%progbits,1" "\n" \ | ^ ./include/linux/export-internal.h:62:41: note: in expansion of macro ‘__KSYMTAB’ 62 | #define KSYMTAB_FUNC(name, sec, ns) __KSYMTAB(name, KSYM_FUNC(name), sec, ns) | ^~~~~~~~~ .vmlinux.export.c:2020:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 2020 | KSYMTAB_FUNC(bpf_link_get_from_fd, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ .vmlinux.export.c:2022:34: error: expected ‘)’ before ‘BPF_INTERNAL’ 2022 | KSYMTAB_FUNC(kern_sys_bpf, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:45:28: note: in definition of macro ‘__KSYMTAB’ 45 | " .asciz \"" ns "\"" "\n" \ | ^~ .vmlinux.export.c:2022:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 2022 | KSYMTAB_FUNC(kern_sys_bpf, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:41:12: note: to match this ‘(’ 41 | asm(" .section \"__ksymtab_strings\",\"aMS\",%progbits,1" "\n" \ | ^ ./include/linux/export-internal.h:62:41: note: in expansion of macro ‘__KSYMTAB’ 62 | #define KSYMTAB_FUNC(name, sec, ns) __KSYMTAB(name, KSYM_FUNC(name), sec, ns) | ^~~~~~~~~ .vmlinux.export.c:2022:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 2022 | KSYMTAB_FUNC(kern_sys_bpf, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ===================================================== # Builds where the incident occurred: ## cros://chromeos-6.6/x86_64/chromeos-intel-pineview.flavour.config+lab-setup+x86-board+CONFIG_MODULE_COMPRESS=n+CONFIG_MODULE_COMPRESS_NONE=y on (x86_64): - compiler: gcc-12 - dashboard: https://d.kernelci.org/build/maestro:680fc27b43948caad95c1492 #kernelci issue maestro:b3bf65712cbf0afb6965b8e30e3b0b32d73bf462 Reported-by: kernelci.org bot <bot(a)kernelci.org> -- This is an experimental report format. Please send feedback in! Talk to us at kernelci(a)lists.linux.dev Made with love by the KernelCI team - https://kernelci.org

4 months, 1 week

1
0
0 0

[REGRESSION] stable-rc/linux-6.12.y: (build) expected ')' in .vmlinux.export.o (.vmlinux.export.c) [logspec:kbu...

by KernelCI bot

Hello, New build issue found on stable-rc/linux-6.12.y: --- expected ')' in .vmlinux.export.o (.vmlinux.export.c) [logspec:kbuild,kbuild.compiler.error] --- - dashboard: https://d.kernelci.org/i/maestro:4c5b6ca45d520d28e9cb7711bd71952a44f4db34 - giturl: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git - commit HEAD: 0f114e4705bd70a1aade95111161a0a24a597879 Log excerpt: ===================================================== .vmlinux.export.c:1649:33: error: expected ')' 1649 | KSYMTAB_FUNC(bpf_map_get, "", ""BPF_INTERNAL""); | ^ .vmlinux.export.c:1649:1: note: to match this '(' 1649 | KSYMTAB_FUNC(bpf_map_get, "", ""BPF_INTERNAL""); | ^ ./include/linux/export-internal.h:62:37: note: expanded from macro 'KSYMTAB_FUNC' 62 | #define KSYMTAB_FUNC(name, sec, ns) __KSYMTAB(name, KSYM_FUNC(name), sec, ns) | ^ ./include/linux/export-internal.h:41:5: note: expanded from macro '__KSYMTAB' 41 | asm(" .section \"__ksymtab_strings\",\"aMS\",%progbits,1" "\n" \ | ^ .vmlinux.export.c:1658:42: error: expected ')' 1658 | KSYMTAB_FUNC(bpf_link_get_from_fd, "", ""BPF_INTERNAL""); | ^ .vmlinux.export.c:1658:1: note: to match this '(' 1658 | KSYMTAB_FUNC(bpf_link_get_from_fd, "", ""BPF_INTERNAL""); | ^ ./include/linux/export-internal.h:62:37: note: expanded from macro 'KSYMTAB_FUNC' 62 | #define KSYMTAB_FUNC(name, sec, ns) __KSYMTAB(name, KSYM_FUNC(name), sec, ns) | ^ ./include/linux/export-internal.h:41:5: note: expanded from macro '__KSYMTAB' 41 | asm(" .section \"__ksymtab_strings\",\"aMS\",%progbits,1" "\n" \ | ^ .vmlinux.export.c:1660:34: error: expected ')' 1660 | KSYMTAB_FUNC(kern_sys_bpf, "", ""BPF_INTERNAL""); | ^ .vmlinux.export.c:1660:1: note: to match this '(' 1660 | KSYMTAB_FUNC(kern_sys_bpf, "", ""BPF_INTERNAL""); | ^ ./include/linux/export-internal.h:62:37: note: expanded from macro 'KSYMTAB_FUNC' 62 | #define KSYMTAB_FUNC(name, sec, ns) __KSYMTAB(name, KSYM_FUNC(name), sec, ns) | ^ ./include/linux/export-internal.h:41:5: note: expanded from macro '__KSYMTAB' 41 | asm(" .section \"__ksymtab_strings\",\"aMS\",%progbits,1" "\n" \ | ^ 3 errors generated. ===================================================== # Builds where the incident occurred: ## x86_64_defconfig+kselftest+x86-board on (x86_64): - compiler: clang-17 - dashboard: https://d.kernelci.org/build/maestro:680fc29843948caad95c14ba #kernelci issue maestro:4c5b6ca45d520d28e9cb7711bd71952a44f4db34 Reported-by: kernelci.org bot <bot(a)kernelci.org> -- This is an experimental report format. Please send feedback in! Talk to us at kernelci(a)lists.linux.dev Made with love by the KernelCI team - https://kernelci.org

4 months, 1 week

1
0
0 0

[REGRESSION] stable-rc/linux-5.15.y: (build) use of undeclared identifier 'MSM_UART_CR_CMD_RESET_RX' in drivers...

by KernelCI bot

Hello, New build issue found on stable-rc/linux-5.15.y: --- use of undeclared identifier 'MSM_UART_CR_CMD_RESET_RX' in drivers/tty/serial/msm_serial.o (drivers/tty/serial/msm_serial.c) [logspec:kbuild,kbuild.compiler.error] --- - dashboard: https://d.kernelci.org/i/maestro:d95ff390762699864781d2727badc1f762a8695e - giturl: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git - commit HEAD: 7e1718e4648c8d93f1738a07033b83f2fd6b43e5 Log excerpt: ===================================================== drivers/tty/serial/msm_serial.c:1737:27: error: use of undeclared identifier 'MSM_UART_CR_CMD_RESET_RX' 1737 | msm_write(&device->port, MSM_UART_CR_CMD_RESET_RX, MSM_UART_CR); | ^ drivers/tty/serial/msm_serial.c:1737:53: error: use of undeclared identifier 'MSM_UART_CR' 1737 | msm_write(&device->port, MSM_UART_CR_CMD_RESET_RX, MSM_UART_CR); | ^ drivers/tty/serial/msm_serial.c:1738:27: error: use of undeclared identifier 'MSM_UART_CR_CMD_RESET_TX' 1738 | msm_write(&device->port, MSM_UART_CR_CMD_RESET_TX, MSM_UART_CR); | ^ drivers/tty/serial/msm_serial.c:1738:53: error: use of undeclared identifier 'MSM_UART_CR' 1738 | msm_write(&device->port, MSM_UART_CR_CMD_RESET_TX, MSM_UART_CR); | ^ drivers/tty/serial/msm_serial.c:1739:27: error: use of undeclared identifier 'MSM_UART_CR_TX_ENABLE' 1739 | msm_write(&device->port, MSM_UART_CR_TX_ENABLE, MSM_UART_CR); | ^ drivers/tty/serial/msm_serial.c:1739:50: error: use of undeclared identifier 'MSM_UART_CR' 1739 | msm_write(&device->port, MSM_UART_CR_TX_ENABLE, MSM_UART_CR); | ^ 6 errors generated. ===================================================== # Builds where the incident occurred: ## defconfig+arm64-chromebook+kselftest on (arm64): - compiler: clang-17 - dashboard: https://d.kernelci.org/build/maestro:680fc0ab43948caad95c0eb7 #kernelci issue maestro:d95ff390762699864781d2727badc1f762a8695e Reported-by: kernelci.org bot <bot(a)kernelci.org> -- This is an experimental report format. Please send feedback in! Talk to us at kernelci(a)lists.linux.dev Made with love by the KernelCI team - https://kernelci.org

4 months, 1 week

1
0
0 0

[REGRESSION] stable-rc/linux-6.12.y: (build) expected ‘)’ before ‘BPF_INTERNAL’ in .vmlinux.export.o (.vmlinux....

by KernelCI bot

Hello, New build issue found on stable-rc/linux-6.12.y: --- expected ‘)’ before ‘BPF_INTERNAL’ in .vmlinux.export.o (.vmlinux.export.c) [logspec:kbuild,kbuild.compiler.error] --- - dashboard: https://d.kernelci.org/i/maestro:46f49bf36be10baf43434c37b3ddb54286312613 - giturl: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git - commit HEAD: 0f114e4705bd70a1aade95111161a0a24a597879 Log excerpt: ===================================================== .vmlinux.export.c:1649:33: error: expected ‘)’ before ‘BPF_INTERNAL’ 1649 | KSYMTAB_FUNC(bpf_map_get, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:45:28: note: in definition of macro ‘__KSYMTAB’ 45 | " .asciz \"" ns "\"" "\n" \ | ^~ .vmlinux.export.c:1649:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 1649 | KSYMTAB_FUNC(bpf_map_get, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:41:12: note: to match this ‘(’ 41 | asm(" .section \"__ksymtab_strings\",\"aMS\",%progbits,1" "\n" \ | ^ ./include/linux/export-internal.h:62:41: note: in expansion of macro ‘__KSYMTAB’ 62 | #define KSYMTAB_FUNC(name, sec, ns) __KSYMTAB(name, KSYM_FUNC(name), sec, ns) | ^~~~~~~~~ .vmlinux.export.c:1649:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 1649 | KSYMTAB_FUNC(bpf_map_get, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ .vmlinux.export.c:1658:42: error: expected ‘)’ before ‘BPF_INTERNAL’ 1658 | KSYMTAB_FUNC(bpf_link_get_from_fd, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:45:28: note: in definition of macro ‘__KSYMTAB’ 45 | " .asciz \"" ns "\"" "\n" \ | ^~ .vmlinux.export.c:1658:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 1658 | KSYMTAB_FUNC(bpf_link_get_from_fd, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:41:12: note: to match this ‘(’ 41 | asm(" .section \"__ksymtab_strings\",\"aMS\",%progbits,1" "\n" \ | ^ ./include/linux/export-internal.h:62:41: note: in expansion of macro ‘__KSYMTAB’ 62 | #define KSYMTAB_FUNC(name, sec, ns) __KSYMTAB(name, KSYM_FUNC(name), sec, ns) | ^~~~~~~~~ .vmlinux.export.c:1658:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 1658 | KSYMTAB_FUNC(bpf_link_get_from_fd, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ .vmlinux.export.c:1660:34: error: expected ‘)’ before ‘BPF_INTERNAL’ 1660 | KSYMTAB_FUNC(kern_sys_bpf, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:45:28: note: in definition of macro ‘__KSYMTAB’ 45 | " .asciz \"" ns "\"" "\n" \ | ^~ .vmlinux.export.c:1660:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 1660 | KSYMTAB_FUNC(kern_sys_bpf, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ./include/linux/export-internal.h:41:12: note: to match this ‘(’ 41 | asm(" .section \"__ksymtab_strings\",\"aMS\",%progbits,1" "\n" \ | ^ ./include/linux/export-internal.h:62:41: note: in expansion of macro ‘__KSYMTAB’ 62 | #define KSYMTAB_FUNC(name, sec, ns) __KSYMTAB(name, KSYM_FUNC(name), sec, ns) | ^~~~~~~~~ .vmlinux.export.c:1660:1: note: in expansion of macro ‘KSYMTAB_FUNC’ 1660 | KSYMTAB_FUNC(kern_sys_bpf, "", ""BPF_INTERNAL""); | ^~~~~~~~~~~~ ===================================================== # Builds where the incident occurred: ## x86_64_defconfig+kselftest+x86-board on (x86_64): - compiler: gcc-12 - dashboard: https://d.kernelci.org/build/maestro:680fc30543948caad95c16c9 ## x86_64_defconfig+lab-setup+x86-board+kselftest on (x86_64): - compiler: gcc-12 - dashboard: https://d.kernelci.org/build/maestro:680fc2f743948caad95c16ba #kernelci issue maestro:46f49bf36be10baf43434c37b3ddb54286312613 Reported-by: kernelci.org bot <bot(a)kernelci.org> -- This is an experimental report format. Please send feedback in! Talk to us at kernelci(a)lists.linux.dev Made with love by the KernelCI team - https://kernelci.org

4 months, 1 week

1
0
0 0

[REGRESSION] stable-rc/linux-5.10.y: (build) use of undeclared label 'err_put' in drivers/usb/chipidea/ci_hdrc_...

by KernelCI bot

Hello, New build issue found on stable-rc/linux-5.10.y: --- use of undeclared label 'err_put' in drivers/usb/chipidea/ci_hdrc_imx.o (drivers/usb/chipidea/ci_hdrc_imx.c) [logspec:kbuild,kbuild.compiler.error] --- - dashboard: https://d.kernelci.org/i/maestro:0f670a2992fd569c8e6d89a8144eab56c6e1abfb - giturl: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git - commit HEAD: bcf9e2b721c5e719f339b23ddfb5b0a0c0727cc9 Log excerpt: ===================================================== drivers/usb/chipidea/ci_hdrc_imx.c:402:10: error: use of undeclared label 'err_put' 402 | goto err_p CC [M] drivers/rtc/rtc-fsl-ftm-alarm.o ut; | ^ 1 error generated. ===================================================== # Builds where the incident occurred: ## defconfig+allmodconfig+CONFIG_FRAME_WARN=2048 on (arm): - compiler: clang-17 - dashboard: https://d.kernelci.org/build/maestro:680fc01743948caad95c0ced #kernelci issue maestro:0f670a2992fd569c8e6d89a8144eab56c6e1abfb Reported-by: kernelci.org bot <bot(a)kernelci.org> -- This is an experimental report format. Please send feedback in! Talk to us at kernelci(a)lists.linux.dev Made with love by the KernelCI team - https://kernelci.org

4 months, 1 week

1
0
0 0

FAILED: patch "[PATCH] usb: chipidea: ci_hdrc_imx: implement usb_phy_init() error" failed to apply to 5.4-stable tree

by gregkh＠linuxfoundation.org

The patch below does not apply to the 5.4-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <stable(a)vger.kernel.org>. To reproduce the conflict and resubmit, you may use the following commands: git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-5.4.y git checkout FETCH_HEAD git cherry-pick -x 8c531e0a8c2d82509ad97c6d3a1e6217c7ed136d # <resolve conflicts, build, test, etc.> git commit -s git send-email --to '<stable(a)vger.kernel.org>' --in-reply-to '2025042802-foil-prepaid-54ec@gregkh' --subject-prefix 'PATCH 5.4.y' HEAD^.. Possible dependencies: thanks, greg k-h ------------------ original commit in Linus's tree ------------------ From 8c531e0a8c2d82509ad97c6d3a1e6217c7ed136d Mon Sep 17 00:00:00 2001 From: Fedor Pchelkin <pchelkin(a)ispras.ru> Date: Sun, 16 Mar 2025 13:26:56 +0300 Subject: [PATCH] usb: chipidea: ci_hdrc_imx: implement usb_phy_init() error handling usb_phy_init() may return an error code if e.g. its implementation fails to prepare/enable some clocks. And properly rollback on probe error path by calling the counterpart usb_phy_shutdown(). Found by Linux Verification Center (linuxtesting.org). Fixes: be9cae2479f4 ("usb: chipidea: imx: Fix ULPI on imx53") Cc: stable <stable(a)kernel.org> Signed-off-by: Fedor Pchelkin <pchelkin(a)ispras.ru> Acked-by: Peter Chen <peter.chen(a)kernel.org> Link: https://lore.kernel.org/r/20250316102658.490340-4-pchelkin@ispras.ru Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> diff --git a/drivers/usb/chipidea/ci_hdrc_imx.c b/drivers/usb/chipidea/ci_hdrc_imx.c index d942b3c72640..4f8bfd242b59 100644 --- a/drivers/usb/chipidea/ci_hdrc_imx.c +++ b/drivers/usb/chipidea/ci_hdrc_imx.c @@ -484,7 +484,11 @@ static int ci_hdrc_imx_probe(struct platform_device *pdev) of_usb_get_phy_mode(np) == USBPHY_INTERFACE_MODE_ULPI) { pdata.flags |= CI_HDRC_OVERRIDE_PHY_CONTROL; data->override_phy_control = true; - usb_phy_init(pdata.usb_phy); + ret = usb_phy_init(pdata.usb_phy); + if (ret) { + dev_err(dev, "Failed to init phy\n"); + goto err_clk; + } } if (pdata.flags & CI_HDRC_SUPPORTS_RUNTIME_PM) @@ -493,7 +497,7 @@ static int ci_hdrc_imx_probe(struct platform_device *pdev) ret = imx_usbmisc_init(data->usbmisc_data); if (ret) { dev_err(dev, "usbmisc init failed, ret=%d\n", ret); - goto err_clk; + goto phy_shutdown; } data->ci_pdev = ci_hdrc_add_device(dev, @@ -502,7 +506,7 @@ static int ci_hdrc_imx_probe(struct platform_device *pdev) if (IS_ERR(data->ci_pdev)) { ret = PTR_ERR(data->ci_pdev); dev_err_probe(dev, ret, "ci_hdrc_add_device failed\n"); - goto err_clk; + goto phy_shutdown; } if (data->usbmisc_data) { @@ -536,6 +540,9 @@ static int ci_hdrc_imx_probe(struct platform_device *pdev) disable_device: ci_hdrc_remove_device(data->ci_pdev); +phy_shutdown: + if (data->override_phy_control) + usb_phy_shutdown(data->phy); err_clk: clk_disable_unprepare(data->clk_wakeup); err_wakeup_clk:

4 months, 1 week

1
0
0 0

FAILED: patch "[PATCH] usb: chipidea: ci_hdrc_imx: implement usb_phy_init() error" failed to apply to 5.10-stable tree

by gregkh＠linuxfoundation.org

The patch below does not apply to the 5.10-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <stable(a)vger.kernel.org>. To reproduce the conflict and resubmit, you may use the following commands: git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-5.10.y git checkout FETCH_HEAD git cherry-pick -x 8c531e0a8c2d82509ad97c6d3a1e6217c7ed136d # <resolve conflicts, build, test, etc.> git commit -s git send-email --to '<stable(a)vger.kernel.org>' --in-reply-to '2025042856-rotten-chatty-2573@gregkh' --subject-prefix 'PATCH 5.10.y' HEAD^.. Possible dependencies: thanks, greg k-h ------------------ original commit in Linus's tree ------------------ From 8c531e0a8c2d82509ad97c6d3a1e6217c7ed136d Mon Sep 17 00:00:00 2001 From: Fedor Pchelkin <pchelkin(a)ispras.ru> Date: Sun, 16 Mar 2025 13:26:56 +0300 Subject: [PATCH] usb: chipidea: ci_hdrc_imx: implement usb_phy_init() error handling usb_phy_init() may return an error code if e.g. its implementation fails to prepare/enable some clocks. And properly rollback on probe error path by calling the counterpart usb_phy_shutdown(). Found by Linux Verification Center (linuxtesting.org). Fixes: be9cae2479f4 ("usb: chipidea: imx: Fix ULPI on imx53") Cc: stable <stable(a)kernel.org> Signed-off-by: Fedor Pchelkin <pchelkin(a)ispras.ru> Acked-by: Peter Chen <peter.chen(a)kernel.org> Link: https://lore.kernel.org/r/20250316102658.490340-4-pchelkin@ispras.ru Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> diff --git a/drivers/usb/chipidea/ci_hdrc_imx.c b/drivers/usb/chipidea/ci_hdrc_imx.c index d942b3c72640..4f8bfd242b59 100644 --- a/drivers/usb/chipidea/ci_hdrc_imx.c +++ b/drivers/usb/chipidea/ci_hdrc_imx.c @@ -484,7 +484,11 @@ static int ci_hdrc_imx_probe(struct platform_device *pdev) of_usb_get_phy_mode(np) == USBPHY_INTERFACE_MODE_ULPI) { pdata.flags |= CI_HDRC_OVERRIDE_PHY_CONTROL; data->override_phy_control = true; - usb_phy_init(pdata.usb_phy); + ret = usb_phy_init(pdata.usb_phy); + if (ret) { + dev_err(dev, "Failed to init phy\n"); + goto err_clk; + } } if (pdata.flags & CI_HDRC_SUPPORTS_RUNTIME_PM) @@ -493,7 +497,7 @@ static int ci_hdrc_imx_probe(struct platform_device *pdev) ret = imx_usbmisc_init(data->usbmisc_data); if (ret) { dev_err(dev, "usbmisc init failed, ret=%d\n", ret); - goto err_clk; + goto phy_shutdown; } data->ci_pdev = ci_hdrc_add_device(dev, @@ -502,7 +506,7 @@ static int ci_hdrc_imx_probe(struct platform_device *pdev) if (IS_ERR(data->ci_pdev)) { ret = PTR_ERR(data->ci_pdev); dev_err_probe(dev, ret, "ci_hdrc_add_device failed\n"); - goto err_clk; + goto phy_shutdown; } if (data->usbmisc_data) { @@ -536,6 +540,9 @@ static int ci_hdrc_imx_probe(struct platform_device *pdev) disable_device: ci_hdrc_remove_device(data->ci_pdev); +phy_shutdown: + if (data->override_phy_control) + usb_phy_shutdown(data->phy); err_clk: clk_disable_unprepare(data->clk_wakeup); err_wakeup_clk:

4 months, 1 week

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

Linux-stable-mirror April 2025