[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#806911: libc-bin: ldconfig segfaults when run using "setarch uname26"



On 2015-12-02 21:30, Aurelien Jarno wrote:
> On 2015-12-02 11:38, Vagrant Cascadian wrote:
> > Package: libc-bin
> > Version: 2.21-1
> > Severity: normal
> > X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org
> > 
> > Apparently, when run with "setarch uname26" or "linux64 --uname-2.6",
> > ldconfig segfaults.
> > 
> >   setarch uname26 ldconfig
> >   FATAL: kernel too old
> >   Segmentation fault
> > 
> > libc-bin version 2.19-22 in stretch does not segfault when run this
> > way.
> > 
> > I haven't tried, but this may also fail similarly when run on an old
> > kernel as well.
> > 
> > At the very least, maybe it shouldn't segfault with old kernels.
> > 
> > The reproducible builds project use "linux64 --uname-2.6" to set a
> > different kernel version for the second build to find bugs in packages
> > that build differently depending on the running kernel version, and it
> > would be nice if this would continue to work.
> 
> This version of the GNU libc requires at least the kernel from wheezy,
> ie kernel 3.2. If you try with an older kernel, you get an "FATAL:
> kernel too old".
> 
> We don't plan to support older kernels, and it should not be a problem
> given stretch is basically wheezy + 2.

On a second thought, even if we are not going support kernel older than
3.2, it is relatively easy to support uname2.6 personality. I have send
a patch upstream for that, let's see the answer.

https://sourceware.org/ml/libc-alpha/2015-12/msg00028.html

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net

Attachment: signature.asc
Description: PGP signature


Reply to: