ACK: [SRU][N/Q][PATCH 0/1] Fix net:tap.c error "buffer overflow detected"
Benjamin Wheeler
benjamin.wheeler at canonical.com
Thu Jan 15 19:56:36 UTC 2026
Acked-by: Benjamin Wheeler <benjamin.wheeler at canonical.com>
On Wed, Jan 7, 2026 at 1:21 PM Alice C. Munduruca
<alice.munduruca at canonical.com> wrote:
>
> [ Impact ]
>
> Currently the kernel testing infrastructure fails consistently
> on net:tap.c, since our C toolchain defaults to
> `-D_FORTIFY_SOURCE=3`. This causes some issues when checked
> functions such as strcpy() are used on kernel objects which do
> not match the standard object model expected by the glibc checked
> functions.
>
> Use an unchecked function such as memcpy() instead so that none
> of the issues described above manifest.
>
> [ Fix ]
>
> resolute: Will be pulled in from upstream
> questing: Cherry picked from 6.19-rc4
> noble: Cherry picked from 6.19-rc4
> jammy: N/A
>
> [ Tests ]
>
> Compiled and pass-tested on amd64.
>
> [ Where problems could occur ]
>
> No real kernel regression potential as this is a kselftest,
> although, since the original test author did not respond for
> comment during the patch review process, it is possible that
> the merge of `rtattr_add_str` and `rtattr_add_strsz` would
> cause some issues, although this is discussed in the commit
> message.
>
> Alice C. Munduruca (1):
> selftests: net: fix "buffer overflow detected" for tap.c
>
> tools/testing/selftests/net/tap.c | 16 +++++-----------
> 1 file changed, 5 insertions(+), 11 deletions(-)
>
> --
> 2.48.1
>
>
> --
> kernel-team mailing list
> kernel-team at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/kernel-team
More information about the kernel-team
mailing list