mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alexey Khoroshilov <khoroshilov@ispras.ru>
Cc: lucien.xin@gmail.com, vyasevich@gmail.com, nhorman@tuxdriver.com,
	marcelo.leitner@gmail.com, davem@davemloft.net,
	linux-sctp@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, ldv-project@linuxtesting.org
Subject: Re: [PATCH] sctp: remove unreachable code from sctp_sf_violation_chunk()
Date: Sun, 07 Nov 2021 19:40:07 +0000	[thread overview]
Message-ID: <163631400791.18215.13246547902490470871.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1636133427-3990-1-git-send-email-khoroshilov@ispras.ru>

Hello:

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

On Fri,  5 Nov 2021 20:30:27 +0300 you wrote:
> sctp_sf_violation_chunk() is not called with asoc argument equal to NULL,
> but if that happens it would lead to NULL pointer dereference
> in sctp_vtag_verify().
> 
> The patch removes code that handles NULL asoc in sctp_sf_violation_chunk().
> 
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
> 
> [...]

Here is the summary with links:
  - sctp: remove unreachable code from sctp_sf_violation_chunk()
    https://git.kernel.org/netdev/net/c/e7ea51cd879c

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



      reply	other threads:[~2021-11-07 19:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02 20:27 [PATCH] sctp: avoid NULL pointer dereference in sctp_sf_violation Alexey Khoroshilov
2021-11-03 12:43 ` Xin Long
2021-11-05 17:30   ` [PATCH] sctp: remove unreachable code from sctp_sf_violation_chunk() Alexey Khoroshilov
2021-11-07 19: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=163631400791.18215.13246547902490470871.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=khoroshilov@ispras.ru \
    --cc=ldv-project@linuxtesting.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=marcelo.leitner@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=vyasevich@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 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®