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

ucm-imx93: dts: add led heartbeat and eth with fec controller #6

Merged
merged 1 commit into from
Sep 27, 2023
Merged

ucm-imx93: dts: add led heartbeat and eth with fec controller #6

merged 1 commit into from
Sep 27, 2023

Conversation

yaakovEntin
Copy link
Contributor

No description provided.

@vraevsky vraevsky merged commit 0466550 into compulab-yokneam:linux-compulab_v6.1.1 Sep 27, 2023
nandra pushed a commit to polytech-com/linux-compulab that referenced this pull request Apr 18, 2024
[ Upstream commit 1947b92464c3268381604bbe2ac977a3fd78192f ]

Parallel testing appears to show a race between allocating and setting
evsel ids. As there is a bounds check on the xyarray it yields a segv
like:

```
AddressSanitizer:DEADLYSIGNAL

=================================================================

==484408==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000010

==484408==The signal is caused by a WRITE memory access.

==484408==Hint: address points to the zero page.

    #0 0x55cef5d4eff4 in perf_evlist__id_hash tools/lib/perf/evlist.c:256
    compulab-yokneam#1 0x55cef5d4f132 in perf_evlist__id_add tools/lib/perf/evlist.c:274
    compulab-yokneam#2 0x55cef5d4f545 in perf_evlist__id_add_fd tools/lib/perf/evlist.c:315
    compulab-yokneam#3 0x55cef5a1923f in store_evsel_ids util/evsel.c:3130
    compulab-yokneam#4 0x55cef5a19400 in evsel__store_ids util/evsel.c:3147
    compulab-yokneam#5 0x55cef5888204 in __run_perf_stat tools/perf/builtin-stat.c:832
    compulab-yokneam#6 0x55cef5888c06 in run_perf_stat tools/perf/builtin-stat.c:960
    compulab-yokneam#7 0x55cef58932db in cmd_stat tools/perf/builtin-stat.c:2878
...
```

Avoid this crash by early exiting the perf_evlist__id_add_fd and
perf_evlist__id_add is the access is out-of-bounds.

Signed-off-by: Ian Rogers <[email protected]>
Cc: Yang Jihong <[email protected]>
Signed-off-by: Namhyung Kim <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Sasha Levin <[email protected]>
nandra pushed a commit to polytech-com/linux-compulab that referenced this pull request Jun 17, 2024
[ Upstream commit f8bbc07ac535593139c875ffa19af924b1084540 ]

vhost_worker will call tun call backs to receive packets. If too many
illegal packets arrives, tun_do_read will keep dumping packet contents.
When console is enabled, it will costs much more cpu time to dump
packet and soft lockup will be detected.

net_ratelimit mechanism can be used to limit the dumping rate.

PID: 33036    TASK: ffff949da6f20000  CPU: 23   COMMAND: "vhost-32980"
 #0 [fffffe00003fce50] crash_nmi_callback at ffffffff89249253
 compulab-yokneam#1 [fffffe00003fce58] nmi_handle at ffffffff89225fa3
 compulab-yokneam#2 [fffffe00003fceb0] default_do_nmi at ffffffff8922642e
 compulab-yokneam#3 [fffffe00003fced0] do_nmi at ffffffff8922660d
 compulab-yokneam#4 [fffffe00003fcef0] end_repeat_nmi at ffffffff89c01663
    [exception RIP: io_serial_in+20]
    RIP: ffffffff89792594  RSP: ffffa655314979e8  RFLAGS: 00000002
    RAX: ffffffff89792500  RBX: ffffffff8af428a0  RCX: 0000000000000000
    RDX: 00000000000003fd  RSI: 0000000000000005  RDI: ffffffff8af428a0
    RBP: 0000000000002710   R8: 0000000000000004   R9: 000000000000000f
    R10: 0000000000000000  R11: ffffffff8acbf64f  R12: 0000000000000020
    R13: ffffffff8acbf698  R14: 0000000000000058  R15: 0000000000000000
    ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018
 compulab-yokneam#5 [ffffa655314979e8] io_serial_in at ffffffff89792594
 compulab-yokneam#6 [ffffa655314979e8] wait_for_xmitr at ffffffff89793470
 compulab-yokneam#7 [ffffa65531497a08] serial8250_console_putchar at ffffffff897934f6
 compulab-yokneam#8 [ffffa65531497a20] uart_console_write at ffffffff8978b605
 compulab-yokneam#9 [ffffa65531497a48] serial8250_console_write at ffffffff89796558
 compulab-yokneam#10 [ffffa65531497ac8] console_unlock at ffffffff89316124
 #11 [ffffa65531497b10] vprintk_emit at ffffffff89317c07
 #12 [ffffa65531497b68] printk at ffffffff89318306
 #13 [ffffa65531497bc8] print_hex_dump at ffffffff89650765
 #14 [ffffa65531497ca8] tun_do_read at ffffffffc0b06c27 [tun]
 #15 [ffffa65531497d38] tun_recvmsg at ffffffffc0b06e34 [tun]
 #16 [ffffa65531497d68] handle_rx at ffffffffc0c5d682 [vhost_net]
 #17 [ffffa65531497ed0] vhost_worker at ffffffffc0c644dc [vhost]
 #18 [ffffa65531497f10] kthread at ffffffff892d2e72
 #19 [ffffa65531497f50] ret_from_fork at ffffffff89c0022f

Fixes: ef3db4a ("tun: avoid BUG, dump packet on GSO errors")
Signed-off-by: Lei Chen <[email protected]>
Reviewed-by: Willem de Bruijn <[email protected]>
Acked-by: Jason Wang <[email protected]>
Reviewed-by: Eric Dumazet <[email protected]>
Acked-by: Michael S. Tsirkin <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Jakub Kicinski <[email protected]>
Signed-off-by: Sasha Levin <[email protected]>
nandra pushed a commit to polytech-com/linux-compulab that referenced this pull request Jun 17, 2024
commit d3b17c6d9dddc2db3670bc9be628b122416a3d26 upstream.

Using completion_done to determine whether the caller has gone
away only works after a complete call.  Furthermore it's still
possible that the caller has not yet called wait_for_completion,
resulting in another potential UAF.

Fix this by making the caller use cancel_work_sync and then freeing
the memory safely.

Fixes: 7d42e097607c ("crypto: qat - resolve race condition during AER recovery")
Cc: <[email protected]> compulab-yokneam#6.8+
Signed-off-by: Herbert Xu <[email protected]>
Reviewed-by: Giovanni Cabiddu <[email protected]>
Signed-off-by: Herbert Xu <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
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