diff options
| author | Eric W. Biederman <ebiederm@xmission.com> | 2008-08-09 15:09:02 -0700 |
|---|---|---|
| committer | Ingo Molnar <mingo@elte.hu> | 2008-08-11 10:37:34 +0200 |
| commit | d388e5fdc461344d04307a3fa83862b9ed429647 (patch) | |
| tree | 61a9a4311b165038423a0f3412e93b8811796c6b /mm | |
| parent | 31343d8a5079cda57ffd539fcf4f00cea344fe98 (diff) | |
| download | linux-3.10-d388e5fdc461344d04307a3fa83862b9ed429647.tar.gz linux-3.10-d388e5fdc461344d04307a3fa83862b9ed429647.tar.bz2 linux-3.10-d388e5fdc461344d04307a3fa83862b9ed429647.zip | |
x86: Restore proper vector locking during cpu hotplug
Having cpu_online_map change during assign_irq_vector can result
in some really nasty and weird things happening. The one that
bit me last time was accessing non existent per cpu memory for non
existent cpus.
This locking was removed in a sloppy x86_64 and x86_32 merge patch.
Guys can we please try and avoid subtly breaking x86 when we are
merging files together?
Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions