summaryrefslogtreecommitdiffstats
path: root/drivers/staging/crystalhd
diff options
context:
space:
mode:
authorNick Kralevich <nnk@google.com>2012-03-07 17:34:38 -0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-03-08 09:37:10 -0800
commitdd09979346813357200adf71b07003fc0a778089 (patch)
tree017ecb0e5f6aeeab8b127e511c6e12e25081327b /drivers/staging/crystalhd
parent3a21138d3f76296ad070a3692d72eb529e7d5d2c (diff)
downloadop-kernel-dev-dd09979346813357200adf71b07003fc0a778089.zip
op-kernel-dev-dd09979346813357200adf71b07003fc0a778089.tar.gz
staging: android: ram_console: honor dmesg_restrict
The Linux kernel has a setting called dmesg_restrict. When true, only processes with CAP_SYSLOG can view the kernel dmesg logs. This helps prevent leaking of kernel information into user space. On Android, it's possible to bypass these restrictions by viewing /proc/last_kmsg. This change makes /proc/last_kmsg require the same permissions as dmesg. CC: Android Kernel Team <kernel-team@android.com> Signed-off-by: Nick Kralevich <nnk@google.com> Signed-off-by: John Stultz <john.stultz@linaro.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/staging/crystalhd')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud