Your message dated Thu, 1 Jan 2026 16:18:28 +0100
with message-id <[email protected]>
and subject line Re: Bug#1022787: libc6-dev: Lintian warns that all mips*el
executables have executable stack
has caused the Debian Bug report #1022787,
regarding libc6-dev: Lintian warns that all mips*el executables have executable
stack
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1022787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022787
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libc6-dev
Version: 2.35-4
Severity: normal
X-Debbugs-Cc: [email protected], [email protected],
[email protected]
User: [email protected]
Usertags: mips mipsel
All mips*el executables and libraries appear to have an executable stack,
resulting in very large numbers of Lintian warnings, particularly for
packages with many small ELF objects like
<https://udd.debian.org/lintian/?packages=samba>.
Jessica Clarke looked into this and found that this is intentionally done
by glibc when targeting minimum kernel 4.8.0 or older with mips hardfloat:
https://github.com/bminor/glibc/blob/595c22ecd8e87a27fd19270ed30fdbae9ad25426/sysdeps/unix/sysv/linux/mips/configure.ac#L138-L143
Debian 9 had a kernel newer than 4.8.0, so I think Debian 12 probably
doesn't need to go that far into backwards compatibility? If the mips
porters agree, then glibc on mips*el should stop forcing an executable
stack, either by increasing the minimal kernel version or by patching
this out. That will provide some security hardening on mips*el.
Or, if the mips porters consider this backwards compatibility to be
more important than the security hardening of a non-executable stack,
then Lintian should stop issuing warnings about the executable stack on
mips*el to improve its signal/noise ratio.
Thanks,
smcv
--- End Message ---
--- Begin Message ---
On 2023-01-16 22:33, Aurelien Jarno wrote:
> Hi,
>
> On 2023-01-16 13:26, Guillem Jover wrote:
> > Hi!
> >
> > On Mon, 2023-01-16 at 12:47:23 +0100, Axel Beckert wrote:
> > > Aurelien Jarno wrote:
> > > > On 2022-10-26 22:09, Aurelien Jarno wrote:
> > > > > Note that the other official architecture still have a kernel
> > > > > compatibility set to 3.2, so that will make a difference between
> > > > > architectures. There are discussions to increase it upstream, but this
> > > > > won't happened for bookworm.
> > > > >
> > > > > On 2022-10-25 21:07, Simon McVittie wrote:
> > > > > > Or, if the mips porters consider this backwards compatibility to be
> > > > > > more important than the security hardening of a non-executable
> > > > > > stack,
> > > > > > then Lintian should stop issuing warnings about the executable
> > > > > > stack on
> > > > > > mips*el to improve its signal/noise ratio.
> > > > >
> > > > > At this stage there is nothing that can be done on the glibc side, the
> > > > > decision has to be taken by the mips porters.
> > > >
> > > > We are getting very close to the toolchain freeze. Any decision about
> > > > that?
> > >
> > > JFYI: There is the request to disable this tag completely on MIPS
> > > architectures in https://bugs.debian.org/1025436
> > >
> > > Now I wonder if this would actually help or worsen the situation for
> > > the glibc maintainers.
> > >
> > > Guillem: You wrote something about "bullseye" in #1025436. I think you
> > > meant "bookworm" instead. Am I right?
> >
> > Indeed, sorry, I was going by Aurelien's comment, but botched the
> > release name. :) But in any case, I'll defer to whatever take Aurelien
> > or other glibc maintainers have on this.
>
> Given we got no decision from the MIPS porters before the toolchain
> freeze, we'll have to live with the executable stack on mips*el for
> bookworm.
>
> Therefore I believe it's a good idea to disable that tag on mips*el on
> the lintian side.
mips* architecture got removed from the archive. Closing the bug.
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
[email protected] http://aurel32.net
--- End Message ---
