Netdev List
 help / color / mirror / Atom feed
From: Nils Juenemann <nils.juenemann@gmail.com>
To: rjethwani@everpuredata.com
Cc: borisp@nvidia.com, davem@davemloft.net, edumazet@google.com,
	john.fastabend@gmail.com, kuba@kernel.org, leon@kernel.org,
	mbloch@nvidia.com, netdev@vger.kernel.org,
	nils.juenemann@gmail.com, pabeni@redhat.com, saeedm@nvidia.com,
	sd@queasysnail.net, tariqt@nvidia.com
Subject: Re: [PATCH net-next v14 0/9] tls: Add TLS 1.3 hardware offload support
Date: Wed,  8 Jul 2026 01:23:25 +0200	[thread overview]
Message-ID: <20260707232325.61396-1-nils.juenemann@gmail.com> (raw)
In-Reply-To: <CAKaoeS3misLGVi4wEqQg3OwbisTBfB0zx-i3b81g2-vnOS_UYA@mail.gmail.com>

On Tue, Jul 7, 2026 at 3:38 PM Rishikesh Jethwani <rjethwani@everpuredata.com> wrote:
>
> Could you please send the following from the dump:
[...]

Hi,

The kdump for this event is incomplete -- makedumpfile ran out of disk
space before finishing -- so I cannot run the crash> struct queries
against it. I will capture a full dump if it recurs.

The oops still gives the relevant fault-site state:

    BUG: kernel NULL pointer dereference, address: 0000000000000030
    Oops: 0000 [#1] SMP NOPTI
    CPU: 9 Comm: swapper/9  7.1.0-rc2+ #4  (mlx5 ConnectX-6 Dx)
    RIP: 0010:mlx5e_ktls_handle_rx_skb+0x10a/0x2d0 [mlx5_core]
    Code: 45 0f b7 c0 e8 17 dc 58 e0 49 89 c7 58 4d 85 ff 0f 84 4a ff ff ff 41 0f b6 47 12 3c 06 0f 84 cc 00 00 00 49 8b 87 f8 04 00 00 <48> 8b 40 30 4c 8b a8 08 01 00 00 4d 85 ed 0f 84 b1 00 00 00 49 8b
    RSP: 0018:ffffd4504071cc38 EFLAGS: 00010293
    RAX: 0000000000000000 RBX: ffff8dca063b5500 RCX: 0000000000000000
    RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
    RBP: ffffd4504071cc68 R08: 0000000000000000 R09: 0000000000000000
    R10: 0000000000000076 R11: 0000000000000000 R12: ffff8dcaaf984000
    R13: 000000000000000e R14: ffff8dc8383605e2 R15: ffff8dc801b33200
    CR2: 0000000000000030
    Call Trace:
     mlx5e_build_rx_skb+0x6fa/0xbf0 [mlx5_core]
     mlx5e_handle_rx_cqe_mpwrq+0x120/0x2a0 [mlx5_core]
     mlx5e_poll_rx_cq+0xa1/0x920 [mlx5_core]
     mlx5e_napi_poll+0x118/0x7e0 [mlx5_core] (softirq)

Decoded faulting instructions:

    49 8b 87 f8 04 00 00   mov 0x4f8(%r15),%rax   ; icsk_ulp_data
    48 8b 40 30            mov 0x30(%rax),%rax    ; priv_ctx_rx

So R15 is sk:

    sk = ffff8dc801b33200

The fault site reloads icsk_ulp_data from sk+0x4f8, gets RAX=0, and then
faults on the priv_ctx_rx load. CR2=0x30 matches that load.

This is the direct tls_get_ctx(sk) use in resync_update_sn()
(ktls_rx.c:553). It is a fresh icsk_ulp_data load at the fault site, not
a value CSE'd from the earlier access via resync_queue_get_psv()
(ktls_rx.c:486).

So I still think this is consistent with icsk_ulp_data being cleared
between the two reads, with the second dereference missing a NULL check.

Thanks,
Nils

  reply	other threads:[~2026-07-07 23:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15 21:27 [PATCH net-next v14 0/9] tls: Add TLS 1.3 hardware offload support Rishikesh Jethwani
2026-05-15 21:27 ` [PATCH v14 1/9] net: tls: reject TLS 1.3 offload in chcr_ktls and nfp drivers Rishikesh Jethwani
2026-05-15 21:27 ` [PATCH v14 2/9] net/mlx5e: add TLS 1.3 hardware offload support Rishikesh Jethwani
2026-05-15 21:27 ` [PATCH v14 3/9] tls: " Rishikesh Jethwani
2026-05-15 21:27 ` [PATCH v14 4/9] tls: split tls_set_sw_offload into init and finalize stages Rishikesh Jethwani
2026-05-15 21:27 ` [PATCH v14 5/9] tls: prep helpers and refactors for HW offload KeyUpdate Rishikesh Jethwani
2026-05-15 21:27 ` [PATCH v14 6/9] tls: device: add TX KeyUpdate support Rishikesh Jethwani
2026-05-25 21:16   ` Jakub Kicinski
2026-06-17 22:32     ` Rishikesh Jethwani
2026-06-17 22:56       ` Jakub Kicinski
2026-05-15 21:27 ` [PATCH v14 7/9] tls: device: add RX " Rishikesh Jethwani
2026-05-25 21:16   ` Jakub Kicinski
2026-06-17 22:36     ` Rishikesh Jethwani
2026-05-15 21:27 ` [PATCH v14 8/9] tls: device: add tracepoints for RX KeyUpdate path Rishikesh Jethwani
2026-05-15 21:27 ` [PATCH v14 9/9] selftests: net: add TLS hardware offload test Rishikesh Jethwani
2026-05-25 21:16   ` Jakub Kicinski
2026-05-17 22:21 ` [PATCH net-next v14 0/9] tls: Add TLS 1.3 hardware offload support Sabrina Dubroca
2026-06-27 21:06 ` Nils Juenemann
2026-07-06 22:14   ` Rishikesh Jethwani
2026-07-07 19:34     ` Nils Juenemann
2026-07-05 10:44 ` Nils Juenemann
2026-07-07 22:38   ` Rishikesh Jethwani
2026-07-07 23:23     ` Nils Juenemann [this message]
2026-07-08  0:02       ` Nils Juenemann
2026-07-08  0:31         ` Rishikesh Jethwani
2026-07-08  6:03           ` Nils Juenemann
2026-07-10 17:56             ` Rishikesh Jethwani

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260707232325.61396-1-nils.juenemann@gmail.com \
    --to=nils.juenemann@gmail.com \
    --cc=borisp@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rjethwani@everpuredata.com \
    --cc=saeedm@nvidia.com \
    --cc=sd@queasysnail.net \
    --cc=tariqt@nvidia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox