Skip to content

swapper fixes (Was: kernel panic on kill(0, SIGTERM) with PGID == 0)

Oleg Nesterov lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest4 patches 10 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4INIT_TASK() should initialize ->thread_group listinclude/linux/init_task.h+1 -03 replies
2/4pids: init_struct_pid.tasks should never see the swapper processinclude/linux/init_task.h+4 -42 replies
3/4pids: fix fork_idle() to setup ->pids correctlykernel/fork.c+13 -11 reply
4/4INIT_SIGHAND: use SIG_DFL instead of NULLinclude/linux/init_task.h+1 -11 reply

Reviews trailers per patch

All 4 patches have a Reviewed-by or Acked-by of their own; the series has one for all of them.

PatchMathias KrauseRoland McGrathSerge E. HallynSukadev Bhattiprolu
SeriesA-b
1/4Reported-and-tested-by A-b A-b
2/4A-b
3/4A-b
4/4A-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 4 reviewers.

Read the v1 thread

Cover letter [PATCH 0/4] swapper fixes (Was: kernel panic on kill(0, SIGTERM) with PGID == 0)

Hello,

Mathias Krause reports that a buggy (or special) /sbin/init can crash the kernel if it sends a signal to its pgrp/sid before it changes its initial (0,0) pids. See the changelog for 1/4.

git-bisect blames "start the global /sbin/init with 0,0 special pids" commit 430c623121ea88ca80595c99fdc63b7f8a803ae5, but in fact the problem was caused by another change, see 2/4.

The patches do not depend on each other, 3/4 fixes another problem, 4/4 is purely cosmetic.

Oleg.