Searched hist:fade4dc49101e3b68fb375fd2b00d0ef1f31a36f (Results 1 – 3 of 3) sorted by relevance
| /linux/arch/s390/include/asm/ |
| H A D | sysinfo.h | diff fade4dc49101e3b68fb375fd2b00d0ef1f31a36f Tue Sep 04 14:26:03 CEST 2012 Heiko Carstens <heiko.carstens@de.ibm.com> s390/sysinfo,topology: fix cpu topology maximum nesting detection
The maximum nesting of the cpu topology is evaluated when /proc/sysinfo
is the first time read. This happens without a lock and a concurrent
reader on a different cpu can see and use an invalid intermediate value.
Besides the fact that this race is quite unlikely the worst thing that
could happen is that /proc/sysinfo would contain bogus information about
the machine's cpu topology.
Nevertheless this should be fixed. So move the detection code to the
early machine detection code and since now the value is early available
use it in the topology code as well.
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
|
| /linux/arch/s390/kernel/ |
| H A D | topology.c | diff fade4dc49101e3b68fb375fd2b00d0ef1f31a36f Tue Sep 04 14:26:03 CEST 2012 Heiko Carstens <heiko.carstens@de.ibm.com> s390/sysinfo,topology: fix cpu topology maximum nesting detection
The maximum nesting of the cpu topology is evaluated when /proc/sysinfo
is the first time read. This happens without a lock and a concurrent
reader on a different cpu can see and use an invalid intermediate value.
Besides the fact that this race is quite unlikely the worst thing that
could happen is that /proc/sysinfo would contain bogus information about
the machine's cpu topology.
Nevertheless this should be fixed. So move the detection code to the
early machine detection code and since now the value is early available
use it in the topology code as well.
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
|
| H A D | early.c | diff fade4dc49101e3b68fb375fd2b00d0ef1f31a36f Tue Sep 04 14:26:03 CEST 2012 Heiko Carstens <heiko.carstens@de.ibm.com> s390/sysinfo,topology: fix cpu topology maximum nesting detection
The maximum nesting of the cpu topology is evaluated when /proc/sysinfo
is the first time read. This happens without a lock and a concurrent
reader on a different cpu can see and use an invalid intermediate value.
Besides the fact that this race is quite unlikely the worst thing that
could happen is that /proc/sysinfo would contain bogus information about
the machine's cpu topology.
Nevertheless this should be fixed. So move the detection code to the
early machine detection code and since now the value is early available
use it in the topology code as well.
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
|