linux-kernel - hotplug cpu: PATCHes for 3 issues

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <4651FC58.mailxOW91VRGMT@eag09.americas.sgi.com>
Date:	Mon, 21 May 2007 15:08:56 -0500
From:	cpw@....com (Cliff Wickman)
To:	linux-kernel@...r.kernel.org
Subject: hotplug cpu: PATCHes for 3 issues



In the 2.6.21 kernel there are still 3 hotplug issues that are cpuset-
related, and that I find to still be problems.   And for which I offer
patches.

These have been submitted before, and subsequently cleaned up per
comments received.  I'm resubmitting all 3 for consideration and further
comment.

1)  [PATCH 1/1] hotplug cpu: cpusets/sched_domain reconciliation
2)  [PATCH 1/1] hotplug cpu: move tasks in empty cpusets to parent
3)  [PATCH 1/1] hotplug cpu: migrate a task within its cpuset

1) Reconciles cpusets and sched_domains that get out of sync
   due to hotplug disabling and re-enabling of cpu's.
   Tasks can get into infinite hangs without this fix.
     kernel/cpuset.c
     kernel/sched.c 

2) When a cpuset is emptied by disabling its cpus, move tasks to 
   a parent cpuset.
   This is a correction of the current procedure, which moves such
   tasks to the wrong cpuset.
     kernel/cpuset.c

3) Causes a task running on a disabled cpu to migrate to a cpu within
   its cpuset.
   This behavior is particularly important for a NUMA system on which
   tasks have been explicitly placed.
     kernel/sched.c
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/