From: Greg KH <gregkh@linuxfoundation.org>
To: Hardik Garg <hargar@linux.microsoft.com>
Cc: stable@vger.kernel.org, chen.dylane@gmail.com, t-anchiang@microsoft.com
Subject: Re: bpf tool build failure in latest stable-rc 6.1.103-rc3 due to missing backport
Date: Sun, 11 Aug 2024 17:27:40 +0200 [thread overview]
Message-ID: <2024081130-backlight-preseason-5a9f@gregkh> (raw)
In-Reply-To: <1722571545-7009-1-git-send-email-hargar@linux.microsoft.com>
On Thu, Aug 01, 2024 at 09:05:45PM -0700, Hardik Garg wrote:
> bpf tool build fails for the latest stable-rc 6.1.103-rc3
> The error details are as follows:
> prog.c: In function 'load_with_options':
> prog.c:1710:23: warning: implicit declaration of function 'create_and_mount_bpffs_dir' [-Wimplicit-function-declaration]
> 1710 | err = create_and_mount_bpffs_dir(pinmaps);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> CC struct_ops.o
> CC tracelog.o
> CC xlated_dumper.o
> CC jit_disasm.o
> CC disasm.o
> LINK bpftool
> /usr/bin/ld: prog.o: in function `load_with_options':
> prog.c:(.text+0x346a): undefined reference to `create_and_mount_bpffs_dir'
>
> The commit causing this failure in 6.1.103-rc3: bc1605fcb33bf7a300cd3ac5c409a16bda1626ba
>
> It appears that the commit from the 6.10 series is missing in this release candidate:
> 478a535ae54a ("bpftool: Mount bpffs on provided dir instead of parent dir")
That commit does not apply to 6.1.y, sorry.
greg k-h
prev parent reply other threads:[~2024-08-11 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 4:05 bpf tool build failure in latest stable-rc 6.1.103-rc3 due to missing backport Hardik Garg
2024-08-03 17:48 ` Akemi Yagi
2024-08-08 18:20 ` Hardik Garg
2024-08-11 10:08 ` Greg KH
2024-08-11 15:27 ` Greg KH [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=2024081130-backlight-preseason-5a9f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=chen.dylane@gmail.com \
--cc=hargar@linux.microsoft.com \
--cc=stable@vger.kernel.org \
--cc=t-anchiang@microsoft.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