[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <aSIYDN5eyKFKoXKL@eldamar.lan>
Date: Sat, 22 Nov 2025 21:07:40 +0100
From: Salvatore Bonaccorso <carnil@...ian.org>
To: Jochen Sprickerhof <jspricke@...ian.org>,
Krzysztof Kozlowski <krzk@...nel.org>,
Sylwester Nawrocki <s.nawrocki@...sung.com>,
Chanwoo Choi <cw00.choi@...sung.com>,
Alim Akhtar <alim.akhtar@...sung.com>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>
Cc: 1121211@...s.debian.org, linux-samsung-soc@...r.kernel.org,
linux-clk@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: Bug#1121211: UBSAN: array-index-out-of-bounds in
/build/reproducible-path/linux-6.17.8/drivers/clk/samsung/clk-exynos-clkout.c:178:18
Hi,
Jochen reported the folowing while booting 6.17.8 based kernel in
Debian:
On Sat, Nov 22, 2025 at 07:19:06PM +0100, Jochen Sprickerhof wrote:
> Package: src:linux
> Version: 6.17.8-1
> Severity: normal
>
> First time booting into 6.17.8-1 and first time I see UBSAN in my logs:
>
> [Nov21 08:31] Booting Linux on physical CPU 0x100
> [ +0,012977] ------------[ cut here ]------------
> [ +0,000017] UBSAN: array-index-out-of-bounds in /build/reproducible-path/linux-6.17.8/drivers/clk/samsung/clk-exynos-clkout.c:178:18
> [ +0,000038] index 0 is out of range for type 'clk_hw *[*]'
> [ +0,000025] CPU: 4 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.17.8+deb14-armmp #1 NONE Debian 6.17.8-1
> [ +0,000018] Hardware name: Samsung Exynos (Flattened Device Tree)
> [ +0,000007] Call trace:
> [ +0,000009] unwind_backtrace from show_stack+0x18/0x1c
> [ +0,000042] show_stack from dump_stack_lvl+0x54/0x68
> [ +0,000036] dump_stack_lvl from ubsan_epilogue+0x8/0x34
> [ +0,000025] ubsan_epilogue from __ubsan_handle_out_of_bounds+0x88/0x8c
> [ +0,000024] __ubsan_handle_out_of_bounds from exynos_clkout_probe+0x38c/0x428
> [ +0,000029] exynos_clkout_probe from platform_probe+0x64/0x98
> [ +0,000034] platform_probe from really_probe+0xd8/0x3ac
> [ +0,000031] really_probe from __driver_probe_device+0x94/0x1dc
> [ +0,000027] __driver_probe_device from driver_probe_device+0x3c/0xd8
> [ +0,000027] driver_probe_device from __driver_attach+0xd8/0x1d8
> [ +0,000028] __driver_attach from bus_for_each_dev+0x84/0xd4
> [ +0,000026] bus_for_each_dev from bus_add_driver+0xf4/0x218
> [ +0,000023] bus_add_driver from driver_register+0x8c/0x140
> [ +0,000027] driver_register from do_one_initcall+0x50/0x24c
> [ +0,000023] do_one_initcall from kernel_init_freeable+0x288/0x2fc
> [ +0,000022] kernel_init_freeable from kernel_init+0x24/0x140
> [ +0,000022] kernel_init from ret_from_fork+0x14/0x28
> [ +0,000015] Exception stack(0xf0835fb0 to 0xf0835ff8)
> [ +0,000012] 5fa0: 00000000 00000000 00000000 00000000
> [ +0,000011] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> [ +0,000009] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000
> [ +0,000007] ---[ end trace ]---
> [ +0,000226] ------------[ cut here ]------------
> [ +0,000012] UBSAN: array-index-out-of-bounds in /build/reproducible-path/linux-6.17.8/drivers/clk/samsung/clk-exynos-clkout.c:183:29
> [ +0,000032] index 0 is out of range for type 'clk_hw *[*]'
> [ +0,000021] CPU: 4 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.17.8+deb14-armmp #1 NONE Debian 6.17.8-1
> [ +0,000014] Hardware name: Samsung Exynos (Flattened Device Tree)
> [ +0,000006] Call trace:
> [ +0,000006] unwind_backtrace from show_stack+0x18/0x1c
> [ +0,000032] show_stack from dump_stack_lvl+0x54/0x68
> [ +0,000033] dump_stack_lvl from ubsan_epilogue+0x8/0x34
> [ +0,000023] ubsan_epilogue from __ubsan_handle_out_of_bounds+0x88/0x8c
> [ +0,000020] __ubsan_handle_out_of_bounds from exynos_clkout_probe+0x354/0x428
> [ +0,000024] exynos_clkout_probe from platform_probe+0x64/0x98
> [ +0,000031] platform_probe from really_probe+0xd8/0x3ac
> [ +0,000031] really_probe from __driver_probe_device+0x94/0x1dc
> [ +0,000031] __driver_probe_device from driver_probe_device+0x3c/0xd8
> [ +0,000028] driver_probe_device from __driver_attach+0xd8/0x1d8
> [ +0,000027] __driver_attach from bus_for_each_dev+0x84/0xd4
> [ +0,000025] bus_for_each_dev from bus_add_driver+0xf4/0x218
> [ +0,000023] bus_add_driver from driver_register+0x8c/0x140
> [ +0,000027] driver_register from do_one_initcall+0x50/0x24c
> [ +0,000022] do_one_initcall from kernel_init_freeable+0x288/0x2fc
> [ +0,000019] kernel_init_freeable from kernel_init+0x24/0x140
> [ +0,000020] kernel_init from ret_from_fork+0x14/0x28
> [ +0,000016] Exception stack(0xf0835fb0 to 0xf0835ff8)
> [ +0,000010] 5fa0: 00000000 00000000 00000000 00000000
> [ +0,000009] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> [ +0,000009] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000
> [ +0,000098] ---[ end trace ]---
Can you have a look into it? The downstream report is at
https://bugs.debian.org/1121211
Regards,
Salvatore
Powered by blists - more mailing lists