Make sure the byte order and ABI of the userprogs matches the one of the
kernel, similar to how the bit size is handled.
Otherwise the userprogs may not be executable.
This happens for example on powerpc little endian, or riscv32.

These patches where originally part of my series "kunit: Introduce UAPI
testing framework" [0], but that isn't going anywhere right now and the
patches are useful on their own.

[0] kunit: Introduce UAPI testing framework

Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
---
Thomas Weißschuh (2):
      kbuild: userprogs: avoid duplication of flags inherited from kernel
      kbuild: userprogs: also inherit byte order and ABI from kernel

 Makefile | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)
---
base-commit: 8f5ae30d69d7543eee0d70083daf4de8fe15d585
change-id: 20250813-kbuild-userprogs-bits-03c117da4d50

Best regards,
-- 
Thomas Weißschuh <thomas.weissschuh@linutronix.de>

On Wed, 13 Aug 2025 07:43:39 +0200, Thomas Weißschuh wrote:
> Make sure the byte order and ABI of the userprogs matches the one of the
> kernel, similar to how the bit size is handled.
> Otherwise the userprogs may not be executable.
> This happens for example on powerpc little endian, or riscv32.
> 
> These patches where originally part of my series "kunit: Introduce UAPI
> testing framework" [0], but that isn't going anywhere right now and the
> patches are useful on their own.
> 
> [...]

Applied, thanks!

[1/2] kbuild: userprogs: avoid duplication of flags inherited from kernel
      https://git.kernel.org/kbuild/c/c5afee88548e4
[2/2] kbuild: userprogs: also inherit byte order and ABI from kernel
      https://git.kernel.org/kbuild/c/478494044bb42

Best regards,
-- 
Nathan Chancellor <nathan@kernel.org>

On Wed, Aug 13, 2025 at 07:43:39AM +0200, Thomas Weißschuh wrote:
> Make sure the byte order and ABI of the userprogs matches the one of the
> kernel, similar to how the bit size is handled.
> Otherwise the userprogs may not be executable.
> This happens for example on powerpc little endian, or riscv32.
> 
> These patches where originally part of my series "kunit: Introduce UAPI
> testing framework" [0], but that isn't going anywhere right now and the
> patches are useful on their own.
> 
> [0] kunit: Introduce UAPI testing framework
> ---
> Thomas Weißschuh (2):
>       kbuild: userprogs: avoid duplication of flags inherited from kernel
>       kbuild: userprogs: also inherit byte order and ABI from kernel

Seems reasonable to me. Should I fast track this via kbuild-fixes or
should I just apply it to kbuild-next? I am guessing you only noticed
this in the context of developing [0] so it might not be a big issue in
the wild?

Cheers,
Nathan

On Thu, Aug 14, 2025 at 11:46:46AM -0700, Nathan Chancellor wrote:
> On Wed, Aug 13, 2025 at 07:43:39AM +0200, Thomas Weißschuh wrote:
> > Make sure the byte order and ABI of the userprogs matches the one of the
> > kernel, similar to how the bit size is handled.
> > Otherwise the userprogs may not be executable.
> > This happens for example on powerpc little endian, or riscv32.
> > 
> > These patches where originally part of my series "kunit: Introduce UAPI
> > testing framework" [0], but that isn't going anywhere right now and the
> > patches are useful on their own.
> > 
> > [0] kunit: Introduce UAPI testing framework

[0] https://lore.kernel.org/lkml/20250717-kunit-kselftests-v5-0-442b711cde2e@linutronix.de/

> > ---
> > Thomas Weißschuh (2):
> >       kbuild: userprogs: avoid duplication of flags inherited from kernel
> >       kbuild: userprogs: also inherit byte order and ABI from kernel
> 
> Seems reasonable to me. Should I fast track this via kbuild-fixes or
> should I just apply it to kbuild-next? I am guessing you only noticed
> this in the context of developing [0] so it might not be a big issue in
> the wild?

kbuild-next should be fine.


Thomas