Skip to content

static_call() vs __exit fixes

Peter Zijlstra lkml 1 version Applied

Status from this message: The following commit has been merged into the locking/urgent branch of tip:

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 19 repliesApplied

Patches in v1 Applied

#Subject and filesSizeRepliesApplied
1/3static_call: Fix static_call_set_init()kernel/static_call.c+10 -70 replies
2/3static_call: Align static_call_is_init() patching conditionkernel/static_call.c+4 -105 replies
3/3static_call: Fix static_call_update() sanity checkkernel/jump_label.c kernel/static_call.c+18 -112 replies

Reviews trailers per patch

None of the 3 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.

PatchSumit GargJarkko Sakkinen
SeriesT-b A-b
1/3
2/3
3/3

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH 0/3] static_call() vs __exit fixes

Hi,

After more poking a new set of patches to fix static_call() vs __exit functions. These patches replace the patch I posted yesterday:

https://lkml.kernel.org/r/[email protected]

Since I've reproduced the problem locally, and these patches do seem to fully cure things, I'll shortly queue them for tip/locking/urgent.