linux-kernel - Re: [PATCH 2/6] media: atomisp: gc2235: Fix namespace collision and startup() section placement with -ffunction-sections

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <f60f83b5-342d-4ec5-b0c0-308e6b4ffdcd@kernel.org>
Date: Fri, 21 Nov 2025 14:28:20 +0100
From: Hans de Goede <hansg@...nel.org>
To: Josh Poimboeuf <jpoimboe@...nel.org>, x86@...nel.org
Cc: linux-kernel@...r.kernel.org, Peter Zijlstra <peterz@...radead.org>,
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
 Jiri Slaby <jirislaby@...nel.org>, Mauro Carvalho Chehab <mchehab@...nel.org>
Subject: Re: [PATCH 2/6] media: atomisp: gc2235: Fix namespace collision and
 startup() section placement with -ffunction-sections

Hi,

On 20-Nov-25 9:14 PM, Josh Poimboeuf wrote:
> When compiled with -ffunction-sections (e.g., for LTO, livepatch, dead
> code elimination, AutoFDO, or Propeller), the startup() function gets
> compiled into the .text.startup section (or in some cases
> .text.startup.constprop.0 or .text.startup.isra.0).
> 
> However, the .text.startup and .text.startup.* sections are also used by
> the compiler for __attribute__((constructor)) code.
> 
> This naming conflict causes the vmlinux linker script to wrongly place
> startup() function code in .init.text, which gets freed during boot.
> 
> Some builds have a mix of objects, both with and without
> -ffunctions-sections, so it's not possible for the linker script to
> disambiguate with #ifdef CONFIG_FUNCTION_SECTIONS or similar.  This
> means that "startup" unfortunately needs to be prohibited as a function
> name.
> 
> Rename startup() to gc2235_startup().
> 
> Signed-off-by: Josh Poimboeuf <jpoimboe@...nel.org>

Thanks, patch looks good to me:

Reviewed-by: Hans de Goede <johannes.goede@....qualcomm.com>

Feel free to merge through the x86/tip tree together with the
rest of the series.

Regards,

Hans




> ---
>  drivers/staging/media/atomisp/i2c/atomisp-gc2235.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/staging/media/atomisp/i2c/atomisp-gc2235.c b/drivers/staging/media/atomisp/i2c/atomisp-gc2235.c
> index 6fc39ab95e46..6050637a0def 100644
> --- a/drivers/staging/media/atomisp/i2c/atomisp-gc2235.c
> +++ b/drivers/staging/media/atomisp/i2c/atomisp-gc2235.c
> @@ -491,7 +491,7 @@ static int gc2235_s_power(struct v4l2_subdev *sd, int on)
>  	return ret;
>  }
>  
> -static int startup(struct v4l2_subdev *sd)
> +static int gc2235_startup(struct v4l2_subdev *sd)
>  {
>  	struct gc2235_device *dev = to_gc2235_sensor(sd);
>  	struct i2c_client *client = v4l2_get_subdevdata(sd);
> @@ -556,7 +556,7 @@ static int gc2235_set_fmt(struct v4l2_subdev *sd,
>  		return 0;
>  	}
>  
> -	ret = startup(sd);
> +	ret = gc2235_startup(sd);
>  	if (ret) {
>  		dev_err(&client->dev, "gc2235 startup err\n");
>  		goto err;