Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH net] sctp: account stream padding length for reconf chunk
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <163422180722.1532.7555776041152823149.git-patchwork-notify@kernel.org>
Date:   Thu, 14 Oct 2021 14:30:07 +0000
References: <b97c1f8b0c7ff79ac4ed206fc2c49d3612e0850c.1634156849.git.mleitner@redhat.com>
In-Reply-To: <b97c1f8b0c7ff79ac4ed206fc2c49d3612e0850c.1634156849.git.mleitner@redhat.com>
To:     Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Cc:     netdev@vger.kernel.org, vyasevich@gmail.com, nhorman@tuxdriver.com,
        eiichi.tsukata@nutanix.com, davem@davemloft.net, kuba@kernel.org,
        linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
        lucien.xin@gmail.com
Precedence: bulk

Hello:

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

On Wed, 13 Oct 2021 17:27:29 -0300 you wrote:
> From: Eiichi Tsukata <eiichi.tsukata@nutanix.com>
> 
> sctp_make_strreset_req() makes repeated calls to sctp_addto_chunk()
> which will automatically account for padding on each call. inreq and
> outreq are already 4 bytes aligned, but the payload is not and doing
> SCTP_PAD4(a + b) (which _sctp_make_chunk() did implicitly here) is
> different from SCTP_PAD4(a) + SCTP_PAD4(b) and not enough. It led to
> possible attempt to use more buffer than it was allocated and triggered
> a BUG_ON.
> 
> [...]

Here is the summary with links:
  - [net] sctp: account stream padding length for reconf chunk
    https://git.kernel.org/netdev/net/c/a2d859e3fc97

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