From: patchwork-bot+netdevbpf@kernel.org
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: davem@davemloft.net, kuba@kernel.org,
herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] net: ipv6: fix field-spanning memcpy warning in AH output
Date: Fri, 26 Sep 2025 21:51:53 +0000 [thread overview]
Message-ID: <175892351350.70549.1277028925175371014.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250926053025.2242061-2-steffen.klassert@secunet.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Steffen Klassert <steffen.klassert@secunet.com>:
On Fri, 26 Sep 2025 07:30:09 +0200 you wrote:
> From: Charalampos Mitrodimas <charmitro@posteo.net>
>
> Fix field-spanning memcpy warnings in ah6_output() and
> ah6_output_done() where extension headers are copied to/from IPv6
> address fields, triggering fortify-string warnings about writes beyond
> the 16-byte address fields.
>
> [...]
Here is the summary with links:
- [1/2] net: ipv6: fix field-spanning memcpy warning in AH output
https://git.kernel.org/netdev/net-next/c/2327a3d6f65c
- [2/2] xfrm: xfrm_user: use strscpy() for alg_name
https://git.kernel.org/netdev/net-next/c/9f4f591cd5a4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-09-26 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 5:30 [PATCH 0/2] pull request (net-next): ipsec-next 2025-09-26 Steffen Klassert
2025-09-26 5:30 ` [PATCH 1/2] net: ipv6: fix field-spanning memcpy warning in AH output Steffen Klassert
2025-09-26 21:51 ` patchwork-bot+netdevbpf [this message]
2025-09-26 5:30 ` [PATCH 2/2] xfrm: xfrm_user: use strscpy() for alg_name Steffen Klassert
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=175892351350.70549.1277028925175371014.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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.