From: Nathan Chancellor <nathan@kernel.org>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Nicolas Schier <nsc@kernel.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 2/3] kbuild: Make sure to generate config file
Date: Wed, 21 Jan 2026 22:15:58 -0700 [thread overview]
Message-ID: <20260122051558.GB3770486@ax162> (raw)
In-Reply-To: <1bb9876f-cb1f-e088-cb9d-f76032f0d395@loongson.cn>
On Thu, Jan 22, 2026 at 09:14:07AM +0800, Tiezhu Yang wrote:
> Currently, CONFIG_IKCONFIG_PROC is set by default on LoongArch,
> the above error still exists, it checks /boot/config-* first,
> here is the related code:
>
> tools/testing/selftests/bpf/unpriv_helpers.c:
> static gzFile open_config(void)
> {
> struct utsname uts;
> char buf[PATH_MAX];
> gzFile config;
>
> if (uname(&uts)) {
> perror("uname");
> goto config_gz;
> }
>
> snprintf(buf, sizeof(buf), "/boot/config-%s", uts.release);
> config = gzopen(buf, "rb");
> if (config)
> return config;
> fprintf(stderr, "gzopen %s: %s\n", buf, strerror(errno));
>
> config_gz:
> config = gzopen("/proc/config.gz", "rb");
> if (!config)
> perror("gzopen /proc/config.gz");
> return config;
> }
Ah but it still falls back to /proc/config.gz though, right?
> Yes, this works well for LoongArch. If there is no need to do this for
> all archs, I will only touch arch/loongarch files.
Until there is a wider insistance on including these as part of the
install target, I think it would be best to keep this in arch/loongarch,
as that is the only architecture that would notice in this case.
> By the way, I do not know why it can not generate System.map by the
> installkernel in practice, could you please check it?
Is installkernel a part of the kernel source? I am not sure where to
begin to investigate that. Could be an inaccurate comment as well if
installkernel's implementation has been updated.
Cheers,
Nathan
next prev parent reply other threads:[~2026-01-22 5:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 12:37 [RFC PATCH 0/3] kbuild: Make sure to generate config and System.map Tiezhu Yang
2026-01-20 12:37 ` [RFC PATCH 1/3] MAINTAINERS: Add scripts/install.sh into Kbuild entry Tiezhu Yang
2026-02-04 0:16 ` (subset) " Nathan Chancellor
2026-01-20 12:37 ` [RFC PATCH 2/3] kbuild: Make sure to generate config file Tiezhu Yang
2026-01-21 23:47 ` Nathan Chancellor
2026-01-22 1:14 ` Tiezhu Yang
2026-01-22 5:15 ` Nathan Chancellor [this message]
2026-01-22 8:58 ` Tiezhu Yang
2026-01-20 12:37 ` [RFC PATCH 3/3] kbuild: Make sure to generate System.map file Tiezhu Yang
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=20260122051558.GB3770486@ax162 \
--to=nathan@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsc@kernel.org \
--cc=yangtiezhu@loongson.cn \
/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