| 2018-02-14 08:30:23 |
Raphaël Hertzog |
bug |
|
|
added bug |
| 2018-03-01 19:15:37 |
Peter Ogden |
bug |
|
|
added subscriber Peter Ogden |
| 2018-03-13 15:23:56 |
nuclearsandwich |
bug |
|
|
added subscriber nuclearsandwich |
| 2018-03-13 15:43:42 |
Dominique Belhachemi |
bug |
|
|
added subscriber Dominique Belhachemi |
| 2018-03-14 20:23:43 |
Tully |
bug |
|
|
added subscriber Tully |
| 2018-03-15 11:39:27 |
Peter Maydell |
tags |
|
arm linux-user |
|
| 2018-03-15 15:27:17 |
Matthias Klose |
bug task added |
|
qemu (Ubuntu) |
|
| 2018-03-22 21:45:57 |
Jeremy Bícha |
bug |
|
|
added subscriber Jeremy Bicha |
| 2018-03-22 21:45:59 |
Launchpad Janitor |
qemu (Ubuntu): status |
New |
Confirmed |
|
| 2018-03-23 06:48:58 |
Christian Ehrhardt |
bug |
|
|
added subscriber ChristianEhrhardt |
| 2018-03-23 18:51:09 |
Steve Beattie |
bug |
|
|
added subscriber Steve Beattie |
| 2018-07-25 21:34:03 |
Dan Streetman |
bug |
|
|
added subscriber Dan Streetman |
| 2019-04-08 15:18:36 |
Dan Streetman |
removed subscriber Dan Streetman |
|
|
|
| 2020-01-17 23:52:50 |
Richard Henderson |
qemu (Ubuntu): assignee |
|
Richard Henderson (rth) |
|
| 2020-03-10 09:07:04 |
Laurent Vivier |
qemu: status |
New |
Fix Committed |
|
| 2020-04-30 13:34:24 |
Laurent Vivier |
qemu: status |
Fix Committed |
Fix Released |
|
| 2020-05-01 06:47:21 |
Christian Ehrhardt |
tags |
arm linux-user |
arm linux-user qemu-20.10 |
|
| 2020-05-01 06:48:40 |
Christian Ehrhardt |
qemu (Ubuntu): status |
Confirmed |
Triaged |
|
| 2020-06-17 07:52:53 |
Christian Ehrhardt |
qemu (Ubuntu): assignee |
Richard Henderson (rth) |
Christian Ehrhardt (paelzer) |
|
| 2020-08-01 05:05:56 |
Launchpad Janitor |
qemu (Ubuntu): status |
Triaged |
Fix Released |
|
| 2020-08-01 05:05:56 |
Launchpad Janitor |
cve linked |
|
2020-10702 |
|
| 2020-08-01 05:05:56 |
Launchpad Janitor |
cve linked |
|
2020-10717 |
|
| 2020-08-01 05:05:56 |
Launchpad Janitor |
cve linked |
|
2020-10761 |
|
| 2020-08-01 05:05:56 |
Launchpad Janitor |
cve linked |
|
2020-11102 |
|
| 2020-08-01 05:05:56 |
Launchpad Janitor |
cve linked |
|
2020-11869 |
|
| 2020-08-01 05:05:56 |
Launchpad Janitor |
cve linked |
|
2020-12829 |
|
| 2020-08-01 05:05:56 |
Launchpad Janitor |
cve linked |
|
2020-13253 |
|
| 2020-08-01 05:05:56 |
Launchpad Janitor |
cve linked |
|
2020-13361 |
|
| 2020-08-01 05:05:56 |
Launchpad Janitor |
cve linked |
|
2020-13362 |
|
| 2020-08-01 05:05:56 |
Launchpad Janitor |
cve linked |
|
2020-13659 |
|
| 2020-08-01 05:05:56 |
Launchpad Janitor |
cve linked |
|
2020-13754 |
|
| 2020-08-01 05:05:56 |
Launchpad Janitor |
cve linked |
|
2020-13791 |
|
| 2020-08-01 05:05:56 |
Launchpad Janitor |
cve linked |
|
2020-13800 |
|
| 2020-08-01 05:05:56 |
Launchpad Janitor |
cve linked |
|
2020-15863 |
|
| 2021-04-19 23:03:37 |
Robie Basak |
nominated for series |
|
Ubuntu Focal |
|
| 2021-04-19 23:03:37 |
Robie Basak |
bug task added |
|
qemu (Ubuntu Focal) |
|
| 2021-04-19 23:03:44 |
Robie Basak |
qemu (Ubuntu Focal): status |
New |
Confirmed |
|
| 2021-04-19 23:03:48 |
Robie Basak |
qemu (Ubuntu Focal): status |
Confirmed |
Triaged |
|
| 2021-04-19 23:03:51 |
Robie Basak |
qemu (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2021-04-19 23:04:01 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Server |
| 2021-04-26 09:12:30 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/401771 |
|
| 2021-04-26 09:17:40 |
Christian Ehrhardt |
description |
In Debian unstable, we recently switched bash to be a PIE-compiled binary (for hardening). Unfortunately this resulted in bash being broken when run under qemu-user (for all target architectures, host being amd64 for me).
$ sudo chroot /srv/chroots/sid-i386/ qemu-i386-static /bin/bash
bash: xmalloc: .././shell.c:1709: cannot allocate 10 bytes (0 bytes allocated)
bash has its own malloc implementation based on sbrk():
https://git.savannah.gnu.org/cgit/bash.git/tree/lib/malloc/malloc.c
When we disable this internal implementation and rely on glibc's malloc, then everything is fine. But it might be that glibc has a fallback when sbrk() is not working properly and it might hide the underlying problem in qemu-user.
This issue has also been reported to the bash upstream author and he suggested that the issue might be in qemu-user so I'm opening a ticket here. Here's the discussion with the bash upstream author:
https://lists.gnu.org/archive/html/bug-bash/2018-02/threads.html#00080
You can find the problematic bash binary in that .deb file:
http://snapshot.debian.org/archive/debian/20180206T154716Z/pool/main/b/bash/bash_4.4.18-1_i386.deb
The version of qemu I have been using is 2.11 (Debian package qemu-user-static version 1:2.11+dfsg-1) but I have had reports that the problem is reproducible with older versions (back to 2.8 at least).
Here are the related Debian bug reports:
https://bugs.debian.org/889869
https://bugs.debian.org/865599
It's worth noting that bash used to have this problem (when compiled as a PIE binary) even when run directly but then something got fixed in the kernel and now the problem only appears when run under qemu-user:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518483 |
[Impact]
* The current space reserved can be too small and we can end up
with no space at all for BRK. It can happen to any case, but is
much more likely with the now common PIE binaries.
* Backport the upstream fix which reserves a bit more space while loading
and giving it back after interpreter and stack is loaded.
[Test Plan]
* On x86 run:
sudo apt install -y qemu-user-static docker.io
sudo docker run --rm arm64v8/debian:bullseye bash -c 'apt update && apt install -y wget'
...
Running hooks in /etc/ca-certificates/update.d...
done.
Errors were encountered while processing:
libc-bin
E: Sub-process /usr/bin/dpkg returned an error code (1)
[Where problems could occur]
* Regressions would be around use-cases of linux-user that is
emulation not of a system but of binaries.
Commonly uses for cross-tests and cross-builds so that is the
space to watch for regressions
[Other Info]
* n/a
---
In Debian unstable, we recently switched bash to be a PIE-compiled binary (for hardening). Unfortunately this resulted in bash being broken when run under qemu-user (for all target architectures, host being amd64 for me).
$ sudo chroot /srv/chroots/sid-i386/ qemu-i386-static /bin/bash
bash: xmalloc: .././shell.c:1709: cannot allocate 10 bytes (0 bytes allocated)
bash has its own malloc implementation based on sbrk():
https://git.savannah.gnu.org/cgit/bash.git/tree/lib/malloc/malloc.c
When we disable this internal implementation and rely on glibc's malloc, then everything is fine. But it might be that glibc has a fallback when sbrk() is not working properly and it might hide the underlying problem in qemu-user.
This issue has also been reported to the bash upstream author and he suggested that the issue might be in qemu-user so I'm opening a ticket here. Here's the discussion with the bash upstream author:
https://lists.gnu.org/archive/html/bug-bash/2018-02/threads.html#00080
You can find the problematic bash binary in that .deb file:
http://snapshot.debian.org/archive/debian/20180206T154716Z/pool/main/b/bash/bash_4.4.18-1_i386.deb
The version of qemu I have been using is 2.11 (Debian package qemu-user-static version 1:2.11+dfsg-1) but I have had reports that the problem is reproducible with older versions (back to 2.8 at least).
Here are the related Debian bug reports:
https://bugs.debian.org/889869
https://bugs.debian.org/865599
It's worth noting that bash used to have this problem (when compiled as a PIE binary) even when run directly but then something got fixed in the kernel and now the problem only appears when run under qemu-user:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518483 |
|
| 2021-09-17 04:34:54 |
Sebastian Unger |
bug |
|
|
added subscriber Sebastian Unger |
| 2021-09-20 09:58:43 |
Christian Ehrhardt |
qemu (Ubuntu): assignee |
Christian Ehrhardt (paelzer) |
|
|
| 2021-09-20 09:58:49 |
Christian Ehrhardt |
removed subscriber Ubuntu Server |
|
|
|
| 2021-11-30 08:45:06 |
Christian Ehrhardt |
bug |
|
|
added subscriber Ubuntu Server |
| 2021-11-30 08:45:11 |
Christian Ehrhardt |
tags |
arm linux-user qemu-20.10 |
arm linux-user qemu-20.10 server-next |
|
| 2021-11-30 08:47:13 |
Christian Ehrhardt |
description |
[Impact]
* The current space reserved can be too small and we can end up
with no space at all for BRK. It can happen to any case, but is
much more likely with the now common PIE binaries.
* Backport the upstream fix which reserves a bit more space while loading
and giving it back after interpreter and stack is loaded.
[Test Plan]
* On x86 run:
sudo apt install -y qemu-user-static docker.io
sudo docker run --rm arm64v8/debian:bullseye bash -c 'apt update && apt install -y wget'
...
Running hooks in /etc/ca-certificates/update.d...
done.
Errors were encountered while processing:
libc-bin
E: Sub-process /usr/bin/dpkg returned an error code (1)
[Where problems could occur]
* Regressions would be around use-cases of linux-user that is
emulation not of a system but of binaries.
Commonly uses for cross-tests and cross-builds so that is the
space to watch for regressions
[Other Info]
* n/a
---
In Debian unstable, we recently switched bash to be a PIE-compiled binary (for hardening). Unfortunately this resulted in bash being broken when run under qemu-user (for all target architectures, host being amd64 for me).
$ sudo chroot /srv/chroots/sid-i386/ qemu-i386-static /bin/bash
bash: xmalloc: .././shell.c:1709: cannot allocate 10 bytes (0 bytes allocated)
bash has its own malloc implementation based on sbrk():
https://git.savannah.gnu.org/cgit/bash.git/tree/lib/malloc/malloc.c
When we disable this internal implementation and rely on glibc's malloc, then everything is fine. But it might be that glibc has a fallback when sbrk() is not working properly and it might hide the underlying problem in qemu-user.
This issue has also been reported to the bash upstream author and he suggested that the issue might be in qemu-user so I'm opening a ticket here. Here's the discussion with the bash upstream author:
https://lists.gnu.org/archive/html/bug-bash/2018-02/threads.html#00080
You can find the problematic bash binary in that .deb file:
http://snapshot.debian.org/archive/debian/20180206T154716Z/pool/main/b/bash/bash_4.4.18-1_i386.deb
The version of qemu I have been using is 2.11 (Debian package qemu-user-static version 1:2.11+dfsg-1) but I have had reports that the problem is reproducible with older versions (back to 2.8 at least).
Here are the related Debian bug reports:
https://bugs.debian.org/889869
https://bugs.debian.org/865599
It's worth noting that bash used to have this problem (when compiled as a PIE binary) even when run directly but then something got fixed in the kernel and now the problem only appears when run under qemu-user:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518483 |
[Impact]
* The current space reserved can be too small and we can end up
with no space at all for BRK. It can happen to any case, but is
much more likely with the now common PIE binaries.
* Backport the upstream fix which reserves a bit more space while loading
and giving it back after interpreter and stack is loaded.
[Test Plan]
* On x86 run:
sudo apt install -y qemu-user-static docker.io
sudo docker run --rm arm64v8/debian:bullseye bash -c 'apt update && apt install -y wget'
...
Running hooks in /etc/ca-certificates/update.d...
done.
Errors were encountered while processing:
libc-bin
E: Sub-process /usr/bin/dpkg returned an error code (1)
Second test from bug 1928075
$ sudo qemu-debootstrap --arch=arm64 bullseye bullseye-arm64 http://ftp.debian.org/debian
In the bad case this is failing like
W: Failure trying to run: /sbin/ldconfig
W: See //debootstrap/debootstrap.log for detail
And in that log file you'll see the segfault
$ tail -n 2 bullseye-arm64/debootstrap/debootstrap.log
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault (core dumped)
[Where problems could occur]
* Regressions would be around use-cases of linux-user that is
emulation not of a system but of binaries.
Commonly uses for cross-tests and cross-builds so that is the
space to watch for regressions
[Other Info]
* n/a
---
In Debian unstable, we recently switched bash to be a PIE-compiled binary (for hardening). Unfortunately this resulted in bash being broken when run under qemu-user (for all target architectures, host being amd64 for me).
$ sudo chroot /srv/chroots/sid-i386/ qemu-i386-static /bin/bash
bash: xmalloc: .././shell.c:1709: cannot allocate 10 bytes (0 bytes allocated)
bash has its own malloc implementation based on sbrk():
https://git.savannah.gnu.org/cgit/bash.git/tree/lib/malloc/malloc.c
When we disable this internal implementation and rely on glibc's malloc, then everything is fine. But it might be that glibc has a fallback when sbrk() is not working properly and it might hide the underlying problem in qemu-user.
This issue has also been reported to the bash upstream author and he suggested that the issue might be in qemu-user so I'm opening a ticket here. Here's the discussion with the bash upstream author:
https://lists.gnu.org/archive/html/bug-bash/2018-02/threads.html#00080
You can find the problematic bash binary in that .deb file:
http://snapshot.debian.org/archive/debian/20180206T154716Z/pool/main/b/bash/bash_4.4.18-1_i386.deb
The version of qemu I have been using is 2.11 (Debian package qemu-user-static version 1:2.11+dfsg-1) but I have had reports that the problem is reproducible with older versions (back to 2.8 at least).
Here are the related Debian bug reports:
https://bugs.debian.org/889869
https://bugs.debian.org/865599
It's worth noting that bash used to have this problem (when compiled as a PIE binary) even when run directly but then something got fixed in the kernel and now the problem only appears when run under qemu-user:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518483 |
|
| 2021-11-30 09:25:18 |
Christian Ehrhardt |
qemu (Ubuntu Focal): status |
Triaged |
In Progress |
|
| 2021-11-30 09:25:21 |
Christian Ehrhardt |
qemu (Ubuntu Focal): assignee |
|
Christian Ehrhardt (paelzer) |
|
| 2021-11-30 19:28:10 |
Brian Murray |
qemu (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2021-11-30 19:28:12 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2021-11-30 19:28:15 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2021-11-30 19:28:21 |
Brian Murray |
tags |
arm linux-user qemu-20.10 server-next |
arm linux-user qemu-20.10 server-next verification-needed verification-needed-focal |
|
| 2021-12-01 07:47:03 |
Christian Ehrhardt |
tags |
arm linux-user qemu-20.10 server-next verification-needed verification-needed-focal |
arm linux-user qemu-20.10 server-next verification-done verification-done-focal |
|
| 2021-12-24 15:04:53 |
frank |
bug |
|
|
added subscriber frank |
| 2022-01-04 17:38:50 |
Launchpad Janitor |
qemu (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2022-01-04 17:38:59 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
