summaryrefslogtreecommitdiffstats
path: root/fs/exofs
diff options
context:
space:
mode:
authorMark Rutland <mark.rutland@arm.com>2018-05-21 18:19:49 +0100
committerWill Deacon <will.deacon@arm.com>2018-05-21 18:21:32 +0100
commit1898eb61fbc9703efee886d3abec27a388cf28c3 (patch)
treed32338cd5bbf458f77d7c70a056e18e78236cf60 /fs/exofs
parent8b0c93c20ef78f15d8b760964ff79bda7f68c610 (diff)
downloadlinux-stable-1898eb61fbc9703efee886d3abec27a388cf28c3.tar.gz
linux-stable-1898eb61fbc9703efee886d3abec27a388cf28c3.tar.bz2
linux-stable-1898eb61fbc9703efee886d3abec27a388cf28c3.zip
drivers/perf: arm-ccn: don't log to dmesg in event_init
The ARM CCN PMU driver uses dev_warn() to complain about parameters in the user-provided perf_event_attr. This means that under normal operation (e.g. a single invocation of the perf tool), a number of messages warnings may be logged to dmesg. Tools may issue multiple syscalls to probe for feature support, and multiple applications (from multiple users) can attempt to open events simultaneously, so this is not very helpful, even if a user happens to have access to dmesg. Worse, this can push important information out of the dmesg ring buffer, and can significantly slow down syscall fuzzers, vastly increasing the time it takes to find critical bugs. Demote the dev_warn() instances to dev_dbg(), as is the case for all other PMU drivers under drivers/perf/. Users who wish to debug PMU event initialisation can enable dynamic debug to receive these messages. Signed-off-by: Mark Rutland <mark.rutland@arm.com> Cc: Pawel Moll <pawel.moll@arm.com> Cc: Will Deacon <will.deacon@arm.com> Signed-off-by: Will Deacon <will.deacon@arm.com>
Diffstat (limited to 'fs/exofs')
0 files changed, 0 insertions, 0 deletions