summaryrefslogtreecommitdiff
path: root/drivers/tty
diff options
context:
space:
mode:
authorBenjamin Herrenschmidt <benh@kernel.crashing.org>2013-08-27 16:38:33 +1000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-09-07 22:09:58 -0700
commit501a297b2351addf61311f9ed49dedb10a4fee9e (patch)
tree2ef78ea4b665d9a009933ffa7d1ec1f01181fc4c /drivers/tty
parent45fe50ea3dadb11c5094d71a4f3e3ccc6f41f1c5 (diff)
downloadlinux-3.10-501a297b2351addf61311f9ed49dedb10a4fee9e.tar.gz
linux-3.10-501a297b2351addf61311f9ed49dedb10a4fee9e.tar.bz2
linux-3.10-501a297b2351addf61311f9ed49dedb10a4fee9e.zip
powerpc: Don't Oops when accessing /proc/powerpc/lparcfg without hypervisor
commit f5f6cbb61610b7bf9d9d96db9c3979d62a424bab upstream. /proc/powerpc/lparcfg is an ancient facility (though still actively used) which allows access to some informations relative to the partition when running underneath a PAPR compliant hypervisor. It makes no sense on non-pseries machines. However, currently, not only can it be created on these if the kernel has pseries support, but accessing it on such a machine will crash due to trying to do hypervisor calls. In fact, it should also not do HV calls on older pseries that didn't have an hypervisor either. Finally, it has the plumbing to be a module but is a "bool" Kconfig option. This fixes the whole lot by turning it into a machine_device_initcall that is only created on pseries, and adding the necessary hypervisor check before calling the H_GET_EM_PARMS hypercall Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/tty')
0 files changed, 0 insertions, 0 deletions