aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/sched-migration.py
diff options
context:
space:
mode:
authorDavidlohr Bueso <[email protected]>2016-03-22 14:27:48 -0700
committerLinus Torvalds <[email protected]>2016-03-22 15:36:02 -0700
commita5f4db877177d2a3d7ae62a7bac3a5a27e083d7f (patch)
tree9cda3b63b32e98b041764acc97dd668eac070526 /tools/perf/scripts/python/sched-migration.py
parentdde5cf39d4d2cce71f2997c37210dd624d0e4bf6 (diff)
ipc/sem: make semctl setting sempid consistent
As indicated by bug#112271, Linux sets the sempid value upon semctl, and not only for semop calls. However, within semctl we only do this for SETVAL, leaving SETALL without updating the field, and therefore rather inconsistent behavior when compared to other Unices. There is really no documentation regarding this and therefore users should not make assumptions. With this patch, along with updating semctl.2 manpages, this scenario should become less ambiguous As such, set sempid on SETALL cmd. Also update some in-code documentation, specifying where the sempid is set. Passes ltp and custom testcase where a child (fork) does SETALL to the set. Signed-off-by: Davidlohr Bueso <[email protected]> Reported-by: Philip Semanchuk <[email protected]> Cc: Michael Kerrisk <[email protected]> Cc: PrasannaKumar Muralidharan <[email protected]> Cc: Manfred Spraul <[email protected]> Cc: Herton R. Krzesinski <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/sched-migration.py')
0 files changed, 0 insertions, 0 deletions