[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <165234661164.9393.13826110571393484922.git-patchwork-notify@kernel.org>
Date: Thu, 12 May 2022 09:10:11 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Kees Cook <keescook@...omium.org>
Cc: kuba@...nel.org, edumazet@...gle.com, davem@...emloft.net,
pabeni@...hat.com, lixiaoyan@...gle.com, tariqt@...dia.com,
saeedm@...dia.com, leon@...nel.org, netdev@...r.kernel.org,
linux-hardening@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-rdma@...r.kernel.org
Subject: Re: [PATCH] fortify: Provide a memcpy trap door for sharp corners
Hello:
This patch was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@...hat.com>:
On Tue, 10 May 2022 19:53:01 -0700 you wrote:
> As we continue to narrow the scope of what the FORTIFY memcpy() will
> accept and build alternative APIs that give the compiler appropriate
> visibility into more complex memcpy scenarios, there is a need for
> "unfortified" memcpy use in rare cases where combinations of compiler
> behaviors, source code layout, etc, result in cases where the stricter
> memcpy checks need to be bypassed until appropriate solutions can be
> developed (i.e. fix compiler bugs, code refactoring, new API, etc). The
> intention is for this to be used only if there's no other reasonable
> solution, for its use to include a justification that can be used
> to assess future solutions, and for it to be temporary.
>
> [...]
Here is the summary with links:
- fortify: Provide a memcpy trap door for sharp corners
https://git.kernel.org/netdev/net-next/c/43213daed6d6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists