linux-kernel - Re: [RFC PATCH] tools/nolibc: HACK!: Add basic self relocation for static PIE for m68k nommu FDPIC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAFr9PX=7gMBW3_d5jSHa1A7YMrZwd60P82FzOhG8nxcg+CAVZw@mail.gmail.com>
Date: Mon, 19 Jan 2026 18:58:31 +0900
From: Daniel Palmer <daniel@...ngy.jp>
To: Thomas Weißschuh <linux@...ssschuh.net>
Cc: Greg Ungerer <gerg@...ux-m68k.org>, w@....eu, linux-m68k@...ts.linux-m68k.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] tools/nolibc: HACK!: Add basic self relocation for
 static PIE for m68k nommu FDPIC

Hi Thomas,

On Sat, 17 Jan 2026 at 04:29, Thomas Weißschuh <linux@...ssschuh.net> wrote:
> Nice! Is it sufficient for nolibc-test? If so, can you provide
> instructions for that?

Not yet. I will try it and get back to you.

> > Questions:
> >
> > - My use case is weird/niche but maybe there are uses for static pie nolibc binaries?
> While I would like to defer to the 'uldso' tool from Greg, nolibc
> positions itself as usable for single-binary systems. Requiring a
> different tool would run a bit counter to that.

I tried Greg's uldso and I couldn't get it working just yet but I
think I can get that working.
But I think having something in the kernel source would also be handy.
I worked out how to use it with the prebuilt m68k toolchain on
kernel.org too so everything needed to build nommu binaries could be
sourced from kernel.org.

> In my opinion it depends on the implementation complexity. If we can
> have a simple implementation shared by all architectures, why not.
> >   - If so what would be a cleaner way of implementing this?
>
> Some comments inline.

Thanks. I'll get this working on amd64 so we can see how much arch
specific stuff there is, address the comments and send again maybe
later this week.

Daniel