Bug#930681: stretch-backports kernel unable to execute (some) older (e.g., CentOS 6) binaries

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#930681: stretch-backports kernel unable to execute (some) older (e.g., CentOS 6) binaries

Mihai Moldovan
Package: linux-image-amd64
Version: 4.19.37-3~bpo9+1

Steps to reproduce:

1.) apt-get install mock
2.) [0] /usr/bin/mock -r /etc/mock/epel-6-x86_64.cfg --init
3.) chroot /var/lib/mock/epel-6-x86_64/root/
=> Segmentation fault
=> [53880.200376] bash[25554] vsyscall attempted with vsyscall=none
ip:ffffffffff600400 cs:33 sp:7ffc1e2c4218 ax:ffffffffff600400 si:7ffc1e2c5729 di:0
=> [53880.200483] bash[25554]: segfault at ffffffffff600400 ip ffffffffff600400
sp 00007ffc1e2c4218 error 15
=> [53880.200576] Code: Bad RIP value.

That's a pretty bad one for me, since it makes building packages for
CentOS/RHEL/EPEL 6 on Debian Stretch impossible.

My likeliest explanation is that some kernel configuration option for supporting
older userspace is disabled.

Interestingly, not *all* binaries are crashing. For instance,
chroot /var/lib/mock/epel-6-x86_64/root/ false
is working fine (though utterly useless).


This naturally used to work with the non-backports stretch kernel, however, this
one is too old to support executing (some) binaries from Fedora 30 (mostly found
Qt5 libraries that require at least 4.11 so far, but there might be others), so
I can't really go back.



Mihai

[0] When executing mock as root, be sure to not execute the wrapper binary in
/usr/sbin, but the "real" one in /usr/bin. Hence the full path.


signature.asc (916 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#930681: stretch-backports kernel unable to execute (some) older (e.g., CentOS 6) binaries

Mihai Moldovan
* On 6/18/19 3:22 PM, Bastian Blank wrote:
> See #847154 for the workaround.
Thanks. Seems to work fine.

This triggered another question, though: can I assume that buster kernels are
also affected by that problem by default? Given that the shipped user space is
new enough, I figure that option will be disabled there as well?



Mihai


signature.asc (916 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#930681: stretch-backports kernel unable to execute (some) older (e.g., CentOS 6) binaries

Ben Hutchings-3
On Wed, 2019-06-19 at 00:37 +0200, Mihai Moldovan wrote:
> * On 6/18/19 3:22 PM, Bastian Blank wrote:
> > See #847154 for the workaround.
> Thanks. Seems to work fine.
>
> This triggered another question, though: can I assume that buster kernels are
> also affected by that problem by default? Given that the shipped user space is
> new enough, I figure that option will be disabled there as well?

Yes, the configuration used in buster is the same.

Ben.

--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
                                                         - Albert Camus



signature.asc (849 bytes) Download Attachment