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,
	netdev@vger.kernel.org, eric.dumazet@gmail.com,
	syzkaller@googlegroups.com, chuck.lever@oracle.com
Subject: Re: [PATCH v2 net] net/handshake: fix null-ptr-deref in handshake_nl_done_doit()
Date: Fri, 01 Sep 2023 06:30:25 +0000	[thread overview]
Message-ID: <169354982560.31046.16261510126804963761.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230831084509.1857341-1-edumazet@google.com>

Hello:

This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:

On Thu, 31 Aug 2023 08:45:09 +0000 you wrote:
> We should not call trace_handshake_cmd_done_err() if socket lookup has failed.
> 
> Also we should call trace_handshake_cmd_done_err() before releasing the file,
> otherwise dereferencing sock->sk can return garbage.
> 
> This also reverts 7afc6d0a107f ("net/handshake: Fix uninitialized local variable")
> 
> [...]

Here is the summary with links:
  - [v2,net] net/handshake: fix null-ptr-deref in handshake_nl_done_doit()
    https://git.kernel.org/netdev/net/c/82ba0ff7bf04

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



      parent reply	other threads:[~2023-09-01  6:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31  8:45 [PATCH v2 net] net/handshake: fix null-ptr-deref in handshake_nl_done_doit() Eric Dumazet
2023-08-31 14:20 ` Michal Kubiak
2023-09-01  6:30 ` 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=169354982560.31046.16261510126804963761.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzkaller@googlegroups.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.