All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, jhs@mojatatu.com, xiyou.wangcong@gmail.com,
	jiri@resnulli.us, netdev@vger.kernel.org, eric.dumazet@gmail.com,
	syzbot+f3a497f02c389d86ef16@syzkaller.appspotmail.com
Subject: Re: [PATCH net-next] net: sched: fix TCF_LAYER_TRANSPORT handling in tcf_get_base_ptr()
Date: Tue, 25 Nov 2025 03:10:06 +0000	[thread overview]
Message-ID: <176404020676.167368.632588971771870032.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251121154100.1616228-1-edumazet@google.com>

Hello:

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

On Fri, 21 Nov 2025 15:41:00 +0000 you wrote:
> syzbot reported that tcf_get_base_ptr() can be called while transport
> header is not set [1].
> 
> Instead of returning a dangling pointer, return NULL.
> 
> Fix tcf_get_base_ptr() callers to handle this NULL value.
> 
> [...]

Here is the summary with links:
  - [net-next] net: sched: fix TCF_LAYER_TRANSPORT handling in tcf_get_base_ptr()
    https://git.kernel.org/netdev/net/c/4fe5a00ec707

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



      parent reply	other threads:[~2025-11-25  3:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21 15:41 [PATCH net-next] net: sched: fix TCF_LAYER_TRANSPORT handling in tcf_get_base_ptr() Eric Dumazet
2025-11-21 17:07 ` Jamal Hadi Salim
2025-11-25  3:10 ` 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=176404020676.167368.632588971771870032.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=horms@kernel.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+f3a497f02c389d86ef16@syzkaller.appspotmail.com \
    --cc=xiyou.wangcong@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.