Re: [PATCH v2] init: staging: Fix missing warning/taint on builtin code

On Thu, Jul 04, 2024 at 09:20:49PM -0300, Ágatha Isabelle Chris Moreira Guedes wrote: > +#ifdef CONFIG_STAGING > +/** > + * staging_init_taint() - We need to taint the kernel whenever staging code > + * is initialized (from built-in drivers) or loaded (as modules) and issue > + * a warning the fir

Re: [PATCH v2] init: staging: Fix missing warning/taint on builtin code

Hello, Please disregard this one, there will be a v3 soon. There were some oversights on my side regarding some review points, and also the code itself. On Thu, Jul 04, 2024 at 09:20:49PM GMT, Ágatha Isabelle Chris Moreira Guedes wrote: > diff --git a/init/main.c b/init/main.c > index 206acdde5

[PATCH v2] init: staging: Fix missing warning/taint on builtin code

Fix the absence of warning message and kernel tainting when initializing drivers from the `drivers/staging` subtree from initcalls (when configured as built-in). When such a driver is built as module and the module is loaded, the `load_module()` function taints the kernel to signal code of unknown