diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2014-10-31 12:28:38 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2014-10-31 12:28:38 -0700 |
| commit | bcdfdaee5a0d914fe23220a297952b0c630f7130 (patch) | |
| tree | 5bcb366ad62291d8e56c56bfc1489d325eb527ec /drivers/base | |
| parent | 4f080f05e650ec60d36eaf2d6d9b7b16ffaad083 (diff) | |
| parent | 086ba77a6db00ed858ff07451bedee197df868c9 (diff) | |
| download | linux-bcdfdaee5a0d914fe23220a297952b0c630f7130.tar.bz2 | |
Merge tag 'trace-fixes-v3.18-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
Pull tracing fix from Steven Rostedt:
"ARM has system calls outside the NR_syscalls range, and the generic
tracing system does not support that and without checks, it can cause
an oops to be reported.
Rabin Vincent added checks in the return code on syscall events to
make sure that the system call number is within the range that tracing
knows about, and if not, simply ignores the system call.
The system call tracing infrastructure needs to be rewritten to handle
these cases better, but for now, to keep from oopsing, this patch will
do"
* tag 'trace-fixes-v3.18-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:
tracing/syscalls: Ignore numbers outside NR_syscalls' range
Diffstat (limited to 'drivers/base')
0 files changed, 0 insertions, 0 deletions