ACK: [SRU][N/Q][PATCH 0/1] Fix net:tap.c error "buffer overflow detected"

[Bethany Jamison]

On 1/7/26 12:21 PM, Alice C. Munduruca 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(-)
>
Acked-by: Bethany Jamison <bethany.jamison at canonical.com>