mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Pengtao He <hept.hept.hept@gmail.com>
Cc: borisp@nvidia.com, john.fastabend@gmail.com, kuba@kernel.org,
	davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
	horms@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/tls: fix kernel panic when alloc_page failed
Date: Thu, 15 May 2025 14:50:36 +0000	[thread overview]
Message-ID: <174732063626.3135544.6593619015947519690.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250514132013.17274-1-hept.hept.hept@gmail.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 14 May 2025 21:20:13 +0800 you wrote:
> We cannot set frag_list to NULL pointer when alloc_page failed.
> It will be used in tls_strp_check_queue_ok when the next time
> tls_strp_read_sock is called.
> 
> Unable to handle kernel NULL pointer dereference
> at virtual address 0000000000000028
>  Call trace:
>  tls_strp_check_rcv+0x128/0x27c
>  tls_strp_data_ready+0x34/0x44
>  tls_data_ready+0x3c/0x1f0
>  tcp_data_ready+0x9c/0xe4
>  tcp_data_queue+0xf6c/0x12d0
>  tcp_rcv_established+0x52c/0x798
> 
> [...]

Here is the summary with links:
  - net/tls: fix kernel panic when alloc_page failed
    https://git.kernel.org/netdev/net/c/491deb9b8c4a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2025-05-15 14:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-14 13:20 Pengtao He
2025-05-15 14:50 ` patchwork-bot+netdevbpf [this message]

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=174732063626.3135544.6593619015947519690.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=borisp@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hept.hept.hept@gmail.com \
    --cc=horms@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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

all inboxes | Powered by JetHome®