Re: [PATCH 3/3] static_call: Fix static_call_update() sanity check

[Steven Rostedt]

On Fri, 19 Mar 2021 20:34:24 +0100
Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote:

> On Fri, Mar 19, 2021 at 02:00:05PM -0400, Steven Rostedt wrote:
> > Would making __exit code the same as init code work? That is, load it just
> > like module init code is loaded, and free it when the init code is freed  
> 
> As stated, yes. But it must then also identify as init through
> within_module_init().

I think that's doable. Since the usecases for that appear to be mostly
about "think code may no longer exist after it is used". Thus, having exit
code act just like init code when UNLOAD is not set, appears appropriate.

Jessica, please correct me if I'm wrong.

Thanks,

-- Steve