Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Shung-Hsi Yu <shung-hsi.yu@suse.com>
Cc: Sasha Levin <sashal@kernel.org>, stable@vger.kernel.org
Subject: Re: BPF selftests compilation failure due to selftests-bpf-initialize-operation-name-before-use.patch
Date: Tue, 21 Jul 2026 09:46:54 +0200	[thread overview]
Message-ID: <2026072148-unskilled-falcon-e39e@gregkh> (raw)
In-Reply-To: <al8dSv_OvhwxFCar@u94a>

On Tue, Jul 21, 2026 at 03:21:55PM +0800, Shung-Hsi Yu wrote:
> Hi Sasha,
> 
> I am running into BPF selftests compilation error on 6.18 (but it
> possibly affect other branches as well, haven't check) due to
> selftests-bpf-initialize-operation-name-before-use.patch currently
> sitting in stable-queue:
> 
> /tmp/work/linux-stable/linux-stable/tools/testing/selftests/bpf/prog_tests/verifier_log.c: In function ‘verif_btf_log_subtest’:
> /tmp/work/linux-stable/linux-stable/tools/testing/selftests/bpf/prog_tests/verifier_log.c:320:9: error: implicit declaration of function ‘strscpy’; did you mean ‘strlcpy’? [-Werror=implicit-function-declaration]
>   320 |         strscpy(op_name, "log_fixed", sizeof(op_name));
>       |         ^~~~~~~
>       |         strlcpy
> 
> Can you pick up commit 63c49efc987a ("selftests/bpf: Add simple
> strscpy() implementation") along? I think that should be enough to fix
> the build failure.

Now applied, thanks.

greg k-h

  reply	other threads:[~2026-07-21  7:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21  7:21 BPF selftests compilation failure due to selftests-bpf-initialize-operation-name-before-use.patch Shung-Hsi Yu
2026-07-21  7:46 ` Greg KH [this message]
2026-07-22  0:53 ` Sasha Levin
2026-07-23  2:45   ` Shung-Hsi Yu

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=2026072148-unskilled-falcon-e39e@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=sashal@kernel.org \
    --cc=shung-hsi.yu@suse.com \
    --cc=stable@vger.kernel.org \
    /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