All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Li Zhong <floridsleeves@gmail.com>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, kuba@kernel.org,
	edumazet@google.com, davem@davemloft.net
Subject: Re: [PATCH net-next v3] ethtool: tunnels: check the return value of nla_nest_start()
Date: Fri, 23 Sep 2022 02:40:20 +0000	[thread overview]
Message-ID: <166390082032.27582.9058046418787346317.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220921181716.1629541-1-floridsleeves@gmail.com>

Hello:

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

On Wed, 21 Sep 2022 11:17:16 -0700 you wrote:
> Check the return value of nla_nest_start(). When starting the entry
> level nested attributes, if the tailroom of socket buffer is
> insufficient to store the attribute header and payload, the return value
> will be NULL. It will cause null pointer dereference when entry is used
> in nla_nest_end().
> 
> Signed-off-by: Li Zhong <floridsleeves@gmail.com>
> 
> [...]

Here is the summary with links:
  - [net-next,v3] ethtool: tunnels: check the return value of nla_nest_start()
    https://git.kernel.org/netdev/net-next/c/05cd823863fd

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



      parent reply	other threads:[~2022-09-23  2:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 18:17 [PATCH net-next v3] ethtool: tunnels: check the return value of nla_nest_start() Li Zhong
2022-09-23  2:28 ` Jakub Kicinski
2022-09-23 21:39   ` Li Zhong
2022-09-23  2:40 ` 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=166390082032.27582.9058046418787346317.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=floridsleeves@gmail.com \
    --cc=kuba@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 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.