Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Rustam Abdullaev <rustamabd@gmail.com>
Cc: buildroot@buildroot.org, Andreas Ziegler <br025@umbiko.net>,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH v2 1/1] toolchain/toolchain-external: introduce BR2_TOOLCHAIN_EXTERNAL_UPDATE_LINUX_HEADERS
Date: Sat, 27 Dec 2025 23:24:20 +0100	[thread overview]
Message-ID: <20251227232420.1644a29f@windsurf> (raw)
In-Reply-To: <20251227211415.2269024-1-rustamabd@gmail.com>

Hello Rustam,

Thanks for your patch!

On Sat, 27 Dec 2025 21:14:15 +0000
Rustam Abdullaev <rustamabd@gmail.com> wrote:

> It is important to have matching kernel headers when building packages
> that make use of kernel features such as seccomp, as they depend on
> system call definitions in linux/unistd.h. A typical example of this is
> openssh - building it with the official ARM GNU toolchain and kernel 6.x
> results in a non-working sshd.

Do you have more details on this? Which version of the ARM GNU
toolchain? Which kernel header version do they use? Which kernel
version are you running?

Indeed, there are two cases:

- The kernel headers in the toolchain are newer than the kernel you're
  running => you are doing it wrong, and updating the headers in the
  toolchain are not going to fix the fact that your C library is built
  with headers that are too recent for your kernel (even though I admit
  glibc has some tolerance on this)

- The kernel headers in the toolchain are older than the kernel you're
  running and you're seeing breakage => this is a kernel bug as it
  shouldn't happen.

In both cases, your proposed patch should therefore not be needed.

Could you clarify which situation you're in, so that we can
understand better whether the use-case/issue you're having warrants
this additional complexity?

> Currently restricted to glibc-based toolchains as glibc is backward- and
> forward-compatible with different kernel versions while uClibc and musl
> are not.

Not sure why this matters here though. Could you clarify?

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-12-27 22:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-27 21:14 [Buildroot] [PATCH v2 1/1] toolchain/toolchain-external: introduce BR2_TOOLCHAIN_EXTERNAL_UPDATE_LINUX_HEADERS Rustam Abdullaev
2025-12-27 22:24 ` Thomas Petazzoni via buildroot [this message]
2025-12-28 16:10   ` Rustam
2026-03-14  7:27     ` Andreas Ziegler
2026-02-02 13:41   ` John Ernberg via buildroot
2026-03-13 23:03     ` Romain Naour via buildroot

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=20251227232420.1644a29f@windsurf \
    --to=buildroot@buildroot.org \
    --cc=br025@umbiko.net \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=romain.naour@gmail.com \
    --cc=rustamabd@gmail.com \
    --cc=thomas.petazzoni@bootlin.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