Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix fec initialization problems #21

Merged
merged 1 commit into from
Oct 21, 2014

Conversation

CrawX
Copy link
Contributor

@CrawX CrawX commented Oct 21, 2014

This fixes fec initialization problems observed on the wandboard quad.
Without this fix, the boot process did not work reliably.
Fix proposed by rmk, thanks.

This fixes fec initialization problems observed on the wandboard quad.
Without this fix, the boot process did not work reliably.
Fix proposed by rmk, thanks.
linux4kix added a commit that referenced this pull request Oct 21, 2014
fix fec initialization problems
@linux4kix linux4kix merged commit b839103 into linux4kix:linux-linaro-lsk-v3.14-mx6 Oct 21, 2014
moonman pushed a commit to moonman/linux-imx6-3.14 that referenced this pull request Nov 14, 2014
commit 086ba77a6db00ed858ff07451bedee197df868c9 upstream.

ARM has some private syscalls (for example, set_tls(2)) which lie
outside the range of NR_syscalls.  If any of these are called while
syscall tracing is being performed, out-of-bounds array access will
occur in the ftrace and perf sys_{enter,exit} handlers.

 # trace-cmd record -e raw_syscalls:* true && trace-cmd report
 ...
 true-653   [000]   384.675777: sys_enter:            NR 192 (0, 1000, 3, 4000022, ffffffff, 0)
 true-653   [000]   384.675812: sys_exit:             NR 192 = 1995915264
 true-653   [000]   384.675971: sys_enter:            NR 983045 (76f74480, 76f74000, 76f74b28, 76f74480, 76f76f74, 1)
 true-653   [000]   384.675988: sys_exit:             NR 983045 = 0
 ...

 # trace-cmd record -e syscalls:* true
 [   17.289329] Unable to handle kernel paging request at virtual address aaaaaace
 [   17.289590] pgd = 9e71c000
 [   17.289696] [aaaaaace] *pgd=00000000
 [   17.289985] Internal error: Oops: 5 [#1] PREEMPT SMP ARM
 [   17.290169] Modules linked in:
 [   17.290391] CPU: 0 PID: 704 Comm: true Not tainted 3.18.0-rc2+ linux4kix#21
 [   17.290585] task: 9f4dab00 ti: 9e710000 task.ti: 9e710000
 [   17.290747] PC is at ftrace_syscall_enter+0x48/0x1f8
 [   17.290866] LR is at syscall_trace_enter+0x124/0x184

Fix this by ignoring out-of-NR_syscalls-bounds syscall numbers.

Commit cd0980f "tracing: Check invalid syscall nr while tracing syscalls"
added the check for less than zero, but it should have also checked
for greater than NR_syscalls.

Link: http://lkml.kernel.org/p/1414620418-29472-1-git-send-email-rabin@rab.in

Fixes: cd0980f "tracing: Check invalid syscall nr while tracing syscalls"
Signed-off-by: Rabin Vincent <rabin@rab.in>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
tomlohave pushed a commit to tomlohave/linux-linaro-stable-mx6 that referenced this pull request Feb 21, 2015
…-mx6-thermal

Linux linaro lsk v3.14 mx6 thermal
tomlohave pushed a commit to tomlohave/linux-linaro-stable-mx6 that referenced this pull request Feb 21, 2015
…sk-v3.14-mx6-thermal"

This reverts commit b919ab2, reversing
changes made to ee05b81.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants