Activity log for bug #1844155
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2019-09-16 14:47:19 | Adam Conrad | bug | added bug | ||
| 2019-09-16 14:47:36 | Adam Conrad | bug watch added | https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904385 | ||
| 2019-09-16 14:47:36 | Adam Conrad | bug task added | linux (Debian) | ||
| 2019-09-16 14:53:19 | Andy Whitcroft | linux (Ubuntu): status | New | Confirmed | |
| 2019-09-16 16:03:22 | Bug Watch Updater | linux (Debian): status | Unknown | Fix Released | |
| 2019-10-01 09:02:57 | Kleber Sacilotto de Souza | nominated for series | Ubuntu Xenial | ||
| 2019-10-01 09:02:57 | Kleber Sacilotto de Souza | bug task added | linux (Ubuntu Xenial) | ||
| 2019-10-01 09:03:05 | Kleber Sacilotto de Souza | linux (Ubuntu Xenial): status | New | Confirmed | |
| 2019-10-01 17:53:02 | Juerg Haefliger | description | This seems to have been fixed in 4.15 (finally), but is still an issue in the 4.4 kernel used on our builders, and possibly others as well (needs investigation). The original Debian bug report linked has more info, as well as the patchset on lkml at https://lkml.org/lkml/2018/7/25/409 | [Impact] The arm64 kernel allows one to run aarch32 processes on an aarch64 processor, using the standard 32/64-bit syscall compatibility. However this compat layer does not correctly validate the arguments of the sigaltstack syscall which can result in process failures. [Test Case] The simple reproducer from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904385 triggers a memory allocation error with the current Xenial 4.4 kernel. [Fix] Backport the following two upstream commits: 24951465cbd2 arm64: compat: Provide definition for COMPAT_SIGMINSTKSZ 22839869f21a signal: Introduce COMPAT_SIGMINSTKSZ for use in compat_sys_sigaltstack With these two commits, the reproducer no longer fails. [Regression Potential] Low. the modifications are trivial and the two patches have been in upstream for quite a while. [Original Description] This seems to have been fixed in 4.15 (finally), but is still an issue in the 4.4 kernel used on our builders, and possibly others as well (needs investigation). The original Debian bug report linked has more info, as well as the patchset on lkml at https://lkml.org/lkml/2018/7/25/409 | |
| 2019-10-21 17:36:26 | Khaled El Mously | linux (Ubuntu Xenial): status | Confirmed | Fix Committed | |
| 2019-10-22 16:04:40 | Ubuntu Kernel Bot | tags | verification-needed-xenial | ||
| 2019-11-07 08:15:55 | Adam Conrad | tags | verification-needed-xenial | verification-done-xenial | |
| 2019-11-07 08:17:10 | Adam Conrad | linux (Ubuntu): status | Confirmed | Fix Released | |
| 2019-11-12 22:33:58 | Launchpad Janitor | linux (Ubuntu Xenial): status | Fix Committed | Fix Released | |
| 2019-11-12 22:33:58 | Launchpad Janitor | cve linked | 2018-12207 | ||
| 2019-11-12 22:33:58 | Launchpad Janitor | cve linked | 2019-0154 | ||
| 2019-11-12 22:33:58 | Launchpad Janitor | cve linked | 2019-0155 | ||
| 2019-11-12 22:33:58 | Launchpad Janitor | cve linked | 2019-11135 | ||
| 2019-11-12 22:33:58 | Launchpad Janitor | cve linked | 2019-15098 | ||
| 2019-11-12 22:33:58 | Launchpad Janitor | cve linked | 2019-17052 | ||
| 2019-11-12 22:33:58 | Launchpad Janitor | cve linked | 2019-17053 | ||
| 2019-11-12 22:33:58 | Launchpad Janitor | cve linked | 2019-17054 | ||
| 2019-11-12 22:33:58 | Launchpad Janitor | cve linked | 2019-17055 | ||
| 2019-11-12 22:33:58 | Launchpad Janitor | cve linked | 2019-17056 | ||
| 2019-11-12 22:33:58 | Launchpad Janitor | cve linked | 2019-17666 |
