From: patchwork-bot+netdevbpf@kernel.org
To: Kees Cook <keescook@chromium.org>
Cc: jay.vosburgh@canonical.com, lkp@intel.com, j.vosburgh@gmail.com,
vfalico@gmail.com, andy@greyhouse.net, davem@davemloft.net,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v3] net: bonding: Use strscpy_pad() instead of manually-truncated strncpy()
Date: Thu, 03 Jun 2021 21:30:07 +0000 [thread overview]
Message-ID: <162275580733.14468.13433184773362130626.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210602205820.361846-1-keescook@chromium.org>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Wed, 2 Jun 2021 13:58:20 -0700 you wrote:
> Silence this warning by using strscpy_pad() directly:
>
> drivers/net/bonding/bond_main.c:4877:3: warning: 'strncpy' specified bound 16 equals destination size [-Wstringop-truncation]
> 4877 | strncpy(params->primary, primary, IFNAMSIZ);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Additionally replace other strncpy() uses, as it is considered deprecated:
> https://www.kernel.org/doc/html/latest/process/deprecated.html#strncpy-on-nul-terminated-strings
>
> [...]
Here is the summary with links:
- [v3] net: bonding: Use strscpy_pad() instead of manually-truncated strncpy()
https://git.kernel.org/netdev/net-next/c/43902070fb7b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-06-03 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 20:58 [PATCH v3] net: bonding: Use strscpy_pad() instead of manually-truncated strncpy() Kees Cook
2021-06-03 21: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=162275580733.14468.13433184773362130626.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=j.vosburgh@gmail.com \
--cc=jay.vosburgh@canonical.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=vfalico@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;
as well as URLs for NNTP newsgroup(s).