[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Hey Zhanglei. We do not have a 5.16 Ubuntu kernel. We do have 5.15 kernels. The current mainline version is 5.18 not 5.16. I have built 2 kernels, one 5.18 and one 5.15 kernel for you. 5.15: https://kernel.ubuntu.com/~kmously/kernel-kmously-45afdcc-gwrv/ 5.18: https://kernel.ubuntu.com/~kmously/kernel-kmously-469ac56-or1l/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Thanks Zhanglei. Great. We have identified the problem patch, which is this one: 380cd49e207ba4 ata: ahci: Add Green Sardine vendor ID as board_ahci_mobile But I am not really sure why this patch is causing a problem. The patch only adds one new line as you can see here: https://pastebin.ubuntu.com/p/TDXdRttc4M/plain Looks like it is altering the behaviour of "PCI device ID 1022:7901" which is supposed to be AMD "Green Sardine". From what I found online, "Green Sardine" is an AMD APU (CPU + GPU) but I believe you are using an AMD EPYC server, so I don't understand why you would be affected at all. Looking at the SOS report you provided, I see the device ID for the SATA controller is 1022:7901 even though you are using EPYC. Again, not really sure why. I don't understand why there is a conflict in device IDs like this. I will see if I can find out more information. Do you know if the problem happens with any disk you hotplug, or just this one? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Hello Zhanglei. Thanks. This means: 3000: BUG 3002: NO BUG 3003: NO BUG 3004: NO BUG 3005: BUG 3006: NO BUG There are only 5 patches between 3005 and 3006 so one of them is the problem. You can see the list of patches here: https://pastebin.canonical.com/p/TkvDGcfHWk/plain/ Only one of them seems related to sata which is "ata: ahci: Add Green Sardine vendor ID as board_ahci_mobile" So maybe this is the one. Please test kernel 3007 from here: https://kernel.ubuntu.com/~kmously/kernel-kmously-3b63e74-Mkii/ If this fails, then this will be the last kernel we have to test. Please make sure you are running version 3007. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Hello Zhanglei. Thanks for the update. This means: 3000: BUG 3002: NO BUG 3003: NO BUG 3004: NO BUG 3005: BUG We are getting very close now. Please try version 3006 from this link: https://kernel.ubuntu.com/~kmously/kernel-kmously-c756bab-RGcD/ Please make sure you are running 3006. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Hello again Zhanglei. This means that so far: 3000: BUG 3002: NO BUG 3003: NO BUG 3004: NO BUG You can find kernel 3005 here: https://kernel.ubuntu.com/~kmously/kernel-kmously-039f206-aRqC/ Please ensure you are running version -3005. Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Thanks Zhanglei. I am building 3005 now. It should be ready in about 30 minutes. I will update again soon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964527] Re: Enable CONFIG_UNICODE for linux-gcp
** Changed in: linux-gcp (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964527 Title: Enable CONFIG_UNICODE for linux-gcp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1964527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Thanks Zhanglei. This means that so far: 3000: BUG 3002: NO BUG 3003: NO BUG We are getting closer. This is the remaining set of patches: 00501b41aaf73f (tag: test-3000, tag: fail1) s390/pci: move pseudo-MMIO to prevent MIO overlap 14914e943b0ca5 cpufreq: Fix get_cpu_device() failure in add_cpu_dev_symlink() 02a3dc73620247 rt2x00: do not mark device gone on EPROTO errors during start d0c736f3c95a8e kprobes: Limit max data_size of the kretprobe instances 1101e48029ef8b vrf: Reset IPCB/IP6CB when processing outbound pkts in vrf dev xmit 8ac948debe102a net/smc: Avoid warning of possible recursive locking 844b74044432ab perf report: Fix memory leaks around perf_tip() ef0a82700dd088 perf hist: Fix memory leak of a perf_hpp_fmt 25b5451cf6b834 net: ethernet: dec: tulip: de4x5: fix possible array overflows in type3_infoblock() 79ab9e40571039 net: tulip: de4x5: fix the problem that the array 'lp->phy[8]' may be out of bound 60cbd2bb3e4920 ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port() 380cd49e207ba4 ata: ahci: Add Green Sardine vendor ID as board_ahci_mobile 02ce9dcd0056d0 scsi: iscsi: Unblock session then wake up error handler 39fe9db370a672 thermal: core: Reset previous low and high trip during thermal zone init 9c4257be2b4e87 (tag: test-3004) btrfs: check-integrity: fix a warning on write caching disabled disk 7888748df21e65 s390/setup: avoid using memblock_enforce_memory_limit ec02be4afbaa32 platform/x86: thinkpad_acpi: Fix WWAN device disabled issue after S3 deep ecaf617d2d911f net: return correct error code cf471f304c7bdd atlantic: Fix OOB read and write in hw_atl_utils_fw_rpc_wait ef48e7dac2b4a5 net/smc: Transfer remaining wait queue entries during fallback f5a7ae1664ea55 mac80211: do not access the IV when it was stripped 04e2506c0a0f0e drm/sun4i: fix unmet dependency on RESET_CONTROLLER for PHY_SUN6I_MIPI_DPHY cc02a02a96d745 gfs2: Fix length of holes reported at end-of-file db58cf66b9ed5f can: j1939: j1939_tp_cmd_recv(): check the dst address of TP.CM_BAM 5891df6f755bdc arm64: dts: mcbin: support 2W SFP modules e7ef1451808ba8 of: clk: Make self-contained a8e84f43323809 NFSv42: Fix pagecache invalidation after COPY/CLONE 87243d366e21dd UBUNTU: upstream stable to v5.4.163 8dedcf4867336b Linux 5.4.163 fe61be970fa57f tty: hvc: replace BUG_ON() with negative return value ae65528da134f8 (tag: test-3003, tag: pass2) xen/netfront: don't trust the backend response data blindly The bottom commit (3003) passed and the top commit (3000) failed, so the problem is one of the patches in between. We are now about to test kernel 3004 in the middle. You can find kernel 3004 here: https://kernel.ubuntu.com/~kmously/kernel-kmously-721de44-fWzO/ Please ensure you are running version -3004. Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Hello Zhanglei. Thanks for the update. From my understanding, so far: 3000: BUG 3002: NO BUG I have the next kernel, 3003, available here: https://kernel.ubuntu.com/~kmously/kernel-kmously-8243717-Kutu Once again, please ensure that you are testing with -3003 when testing. Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Hello Zhanglei, Thanks for the update. I am a little surprised that this kernel failed. There are 2 SATA related changes in kernel -100 which I suspected were the root cause. However, the kernel that I provided (version 3000) did NOT contain those patches, so I expected it to work. The patches that I suspected were the cause are: sata_fsl: fix warning in remove_proc_entry when rmmod sata_fsl sata_fsl: fix UAF in sata_fsl_port_stop when rmmod sata_fsl In any case, maybe my assumption was incorrect. We can continue to bisect anyway. I am unable to provide all the kernels in one shot because the next kernel that we should test depends on the results of the test before it. If I give them all in one shot, I would have to give you 270 kernels to test instead of 9. We have already done the first bisect. Now we have 125 patches (instead of 270) so should be another 7 tests at most. The next kernel is available here: https://kernel.ubuntu.com/~kmously/kernel-kmously-440f762-4e4H/ This is version 3002. Please, when the engineer tests this kernel, make sure to type "uname -r" to confirm that it is version 3002. That way we can be 100% sure we are testing the right kernel. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Hello Zhanglei, thanks for confirming the working/broken versions. I am not sure if I will be able to reproduce the issue myself. There are 270 changes between -99 and -100. If you can help me bisect them, we should be able to quickly identify the problem. Would you be able to test the kernels I provide so we can identify the breaking commit? We might need to test up to 9 more kernels. I have built the first test kernel. It can be found at: https://kernel.ubuntu.com/~kmously/kernel-kmously-d60b65f-bspU/ If you can, please install the linux-image, linux-modules and linux- modules-extra packages from the above link and attempt to reproduce the problem. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971576] Re: SATA device hot plug regression on AMD EYPC (Asus) server
Hello @zhanglei-mao thanks for creating the bug report. There is a large time difference between those 5.4 kernels. 5.4.0-42 is from June 2020 and 5.4.0-109 is very recent. Is it possible to find out the first non-working 5.4 kernel? We would need to do a bisect. Do you think you might be able to test the 5.4.0-75 kernel to try to reproduce this problem? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EYPC (Asus) server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964527] Re: Enable CONFIG_UNICODE for linux-gcp
The change for this bug has been committed to the gcp kernel. The next focal/linux-gcp kernel release (5.4.0-1073 or later) should contain the updated configuration. The bionic/linux-gcp-5.4 kernel will receive the update as well. Thanks for reporting the issue, @lhaley, and thanks for your patience! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964527 Title: Enable CONFIG_UNICODE for linux-gcp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1964527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964527] Re: Enable CONFIG_UNICODE for linux-gcp
** Changed in: linux-gcp (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964527 Title: Enable CONFIG_UNICODE for linux-gcp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1964527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964527] Re: Enable CONFIG_UNICODE for linux-gcp
** Changed in: linux-gcp (Ubuntu Focal) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964527 Title: Enable CONFIG_UNICODE for linux-gcp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1964527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925421] Re: arm64 support
** No longer affects: linux-gcp (Ubuntu Bionic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925421 Title: arm64 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1925421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925421] Re: arm64 support
** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-gcp (Ubuntu Groovy) ** No longer affects: linux-gcp (Ubuntu Hirsute) ** No longer affects: linux-gcp (Ubuntu Impish) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925421 Title: arm64 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1925421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
A [ Regression potential ] section was added to the description.
@Łukasz Zemczak let me know if there are other details you would like.
Thank you!
** Description changed:
-
[Impact]
In some cases, ipconfig can take a longer time than the user-specified
timeouts, causing unexpected delays.
[Test Plan]
Any situation where ipconfig encounters an error sending the DHCP packet, it
will automatically set a delay of 10 seconds, which could be longer than the
user-specified timeout. It can be reproduced by creating a dummy interface and
attempting to run ipconfig on it with a timeout value of less than 10:
# ip link add eth1 type dummy
# date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
Thu Nov 18 04:46:13 EST 2021
IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
IP-Config: no response after 2 secs - giving up
Thu Nov 18 04:46:23 EST 2021
^ Notice above, ipconfig thinks that it waited 2 seconds, but the
timestamps show an actual delay of 10 seconds.
[Where problems could occur]
Please see reproduction steps above. We are seeing this in production too
(see comment #2).
[Other Info]
A patch to fix the issue is being proposed here. It is a safe fix - it only
checks before going into sleep that the timeout never exceeds the
user-requested value.
[Original Description]
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again later"
at time equal now + 10 seconds by setting
s->expire = now + 10;
This can happen at any time during the main event loop, which can end up
extending the user-specified timeout if "now + 10" is greater than
"start_time + user-specified-timeout".
I believe a patch like the following is needed to avoid this problem:
--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)
if (timeout > s->expire - now.tv_sec)
timeout = s->expire - now.tv_sec;
+
+ /* Compensate for already-lost time */
+ gettimeofday(, NULL);
+ if (now.tv_sec + timeout > start + loop_timeout) {
+ timeout = loop_timeout - (now.tv_sec - start);
+ printf("Lowered timeout to match user request
= (%d s) \n", timeout);
+ }
}
I believe the current behaviour is buggy. This is confirmed when the
following line is executed:
if (loop_timeout >= 0 &&
now.tv_sec - start >= loop_timeout) {
printf("IP-Config: no response after %d "
"secs - giving up\n", loop_timeout);
rc = -1;
goto bail;
}
'loop_timeout' is the user-specified time-out. With a value of 2, in
case of error, this line prints:
IP-Config: no response after 2 secs - giving up
So it thinks that it waited 2 seconds - however, in reality it had
actually waited for 10 seconds.
The suggested code-change ensures that the timeout that is actually used
never exceeds the user-specified timeout.
+
+
+ [ Regression potential ]
+
+ This change ensures that user-specified timeouts are never exceeded, which is
a problem that appears to happen only in case of interface errors.
+ It may be that someone is relying on current behaviour where they receive
DHCP offers after their specified timeout (but within the 10-second error
timeout). However, 1) that is buggy behaviour and should be exposed. Such a
user would need to update their specified timeout to make it long enough to
receive the DHCP offer (setting the timeout to 10 would keep the existing
behaviour). 2) I think it is unlikely that such a scenario exists at all. The
10-second timeout problem happens when there are problems with the interface
that prevent it from even sending out the DHCP request. I think it is very
unlikely (or even, impossible) that DHCP offers would be received on a dead
interface.
+
+ Based on the above points, I consider the regression potential to be
+ very low for this change. I do not expect anyone who is currently using
+ ipconfig successfully to notice this change.
+
+ I believe the only difference introduced by this is the reduction of
+ delays caused by dead or problematic network interfaces. Those error
+ delays are shortened such that they never exceeed user-specified
+ timeouts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
Hello @Łukasz Zemczak I understand your concern about breaking existing behaviour. I would like to clarify 2 things: 1) The change introduced here only ensures that user-requested timeouts are never exceeded. That means that if something is currently accepting DHCP offers after the specified timeout has expired, then that is buggy behaviour. It would make sense that such behaviour would change after this change. If such a user exists, they would need to change their timeout values so as to be long enough to receive the DHCP offer that they want. I think it makes sense that such buggy behaviour would get exposed with this fix. 2) That said, I consider it very unlikely for that scenario to even exist. The main reason is that the bug (going over the specified timeout) happens in the case where there is a problem bringing up the interface, so the ipconfig logic simply says "try again in 10 seconds" in that case, even if that 10 seconds is longer than the entire specified timeout. Since this happens when there are interface problems, it can be safely assumed that no DHCP offers will be received anyway on that problematic interface (in fact, no DHCP request was even sent out). These 10 seconds are just dead time, basically. So I would consider it unlikely that anyone who is successfully using ipconfig today would even notice a change. This patch should only affect those 10-seconds delays caused by problematic interfaces not normal functioning interfaces, (and even then, it would only affect them if the user-specified timeout is less than 10 seconds). I am not sure what you mean by how it differs from focal+. The last time I checked, the timeout-bug was affecting ipconfig in both focal and bionic (and upstream HEAD). However, we are only interested in Bionic since Focal does not even use ipconfig it uses dhclient instead. I will add a regression-potential section to the description with more info. Thanks. I will try to expand the regression-potential section with additional info about this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965075] Re: arm64 suport
** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oracle (Ubuntu) ** No longer affects: linux-oracle (Ubuntu Bionic) ** No longer affects: linux-oracle (Ubuntu Focal) ** No longer affects: linux-oracle (Ubuntu Jammy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965075 Title: arm64 suport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1965075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965075] [NEW] arm64 suport
Public bug reported: [Impact] No support for arm64 currently [Fix] Add arm64 support, including hardware support patches [Test] Confirm that it boots on desired arm64 hardware, as well as VMs [Regression Potential] This was never working on arm64 so there should be no risk of regression. The requested changes included some refactorings of early memory initialization code (all arches) so this presents a small risk. The changes were tested on arm64 as well amd64. ** Affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965075 Title: arm64 suport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1965075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964527] [NEW] Enable CONFIG_UNICODE for linux-gcp
Public bug reported: See https://lists.ubuntu.com/archives/kernel-team/2022-March/128565.html NOTE: This config is enabled in other gcp kernels and in non-gcp kernels. ** Affects: linux-gcp (Ubuntu) Importance: Undecided Assignee: Khaled El Mously (kmously) Status: New ** Affects: linux-gcp (Ubuntu Focal) Importance: Undecided Assignee: Khaled El Mously (kmously) Status: New ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: klibc (Ubuntu) ** Also affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Focal) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964527 Title: Enable CONFIG_UNICODE for linux-gcp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1964527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953575] Re: Update gvnic driver code
** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953575 Title: Update gvnic driver code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1953575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953575] Re: Update gvnic driver code
** Changed in: linux-gcp (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-gcp (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953575 Title: Update gvnic driver code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1953575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953575] Re: Update gvnic driver code
** Also affects: linux-gcp (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Impish) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux-gcp (Ubuntu Impish) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953575 Title: Update gvnic driver code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1953575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957744] Re: Unable to set correct resolutions on virtual displays
** Tags removed: verification-needed-impish ** Tags added: verification-done-impish ** Tags removed: verification-needed-focal ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957744 Title: Unable to set correct resolutions on virtual displays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1957744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959173] Re: Vulnerability in af_packet handling
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959173 Title: Vulnerability in af_packet handling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1959173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959173] [NEW] Vulnerability in af_packet handling
Public bug reported: CVE-2021-22600 A vulnerability, which was classified as critical, was found in Linux Kernel. Affected is the function packet_set_ring of the file net/packet/af_packet.c. The manipulation with an unknown input leads to a memory corruption vulnerability. This is going to have an impact on confidentiality, integrity, and availability. The weakness was released 01/26/2022. The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2021-22600 since 01/05/2021. The exploitability is told to be easy. It is possible to launch the attack remotely. A authentication is required for exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 01/26/2022). Applying a patch is able to eliminate this problem. The fix is https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=ec6af094ea28f0f2dda1a6a33b14cd57e36a9755 More information at: https://partnerissuetracker.corp.google.com/issues/215427453 ** Affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gke (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** No longer affects: klibc (Ubuntu) ** Also affects: linux-gke (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959173 Title: Vulnerability in af_packet handling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1959173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957744] [NEW] Unable to set correct resolutions on virtual displays
Public bug reported: See https://canonical.lightning.force.com/lightning/r/Case/5004K09qFamQAE/view for more info ** Affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** No longer affects: klibc (Ubuntu) ** Also affects: linux-oracle (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Hirsute) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957744 Title: Unable to set correct resolutions on virtual displays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1957744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled
Hello @Louis, Are you able to confirm whether the 4.15 kernels are affected by this problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956575 Title: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param
I'm not sure I see a panic in the attached kernel log. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953575] [NEW] Update gvnic driver code
Public bug reported: The GCE internal team responsible for gVNIC would like to have driver updates backported for both Ubuntu 18.04 LTS and Ubuntu 20.04 LTS. [Impact] Missing functionality from the Google gvnic driver [Test Plan] Confirm that gvnic module still loads and operates the gvnic driver. More extensive testing done by the gvnic developers at GCE [Regression potential] Possible regression in gvnic behaviour or functionality. Changes are confined to the gvnic driver code so regression potential is limited to gvnic only. List of changes: 3712db620c613 gve: DQO: Configure interrupts on device up a9fd7559a367a gve: Check TX QPL was actually assigned c69a8892d5836 gve: fix the wrong AdminQ buffer overflow check f48adc2842b17 gve: DQO: Remove incorrect prefetch 98fd04939ae7e gve: Simplify code and axe the use of a deprecated API 56c0904d8491d gve: Propagate error codes to caller 86cd2b58d1e63 gve: DQO: Fix off by one in gve_rx_dqo() ea364622fb118 gve: Fix warnings reported for DQO patchset 8890e8783c6e6 gve: DQO: Add RX path abfc55f80d423 gve: DQO: Add TX path ef63867982913 gve: DQO: Add ring allocation and initialization dc3e0aef11bf0 gve: DQO: Add core netdev features 873fd9825efd7 gve: Update adminq commands to support DQO queues 543dc0e670472 gve: Add DQO fields for core data structures b580730931348 gve: Add dqo descriptors 74e123d3c62b2 gve: Add support for DQO RX PTYPE map a9a3bfdd5f679 gve: adminq: DQO specific device descriptor logic 3e6d068c103f8 gve: Introduce per netdev `enum gve_queue_format` a6b09c93c1735 gve: Introduce a new model for device options 34d6b75678979 gve: Add support for raw addressing in the tx path 30b6221596699 Revert "gve: Check TX QPL was actually assigned" 98478993bb3f9 gve: Make gve_rx_slot_page_info.page_offset an absolute offset ff4b20bb7e5f4 gve: gve_rx_copy: Move padding to an argument 5fc5c482008b5 gve: Move some static functions to a common file ed1e0daeee1ac gve: Rx Buffer Recycling da57760d6370d gve: Add support for raw addressing to the rx path b512608f33d8e gve: Add support for raw addressing device option e85394c77cdce gve: Enable Link Speed Reporting in the driver. 8961791d8ba16 gve: Batch AQ commands for creating and destroying queues. 50bafd6d5a041 gve: NIC stats for report-stats and for ethtool feccb84085904 gve: Add Gvnic stats AQ command and ethtool show/set-priv-flags. 08578185ab296 gve: Use dev_info/err instead of netif_info/err. 613ed2d16246f gve: Add stats for gve. 250d220740d21 gve: Get and set Rx copybreak via ethtool ** Affects: linux-gcp (Ubuntu) Importance: Undecided Assignee: Khaled El Mously (kmously) Status: In Progress ** Affects: linux-gcp (Ubuntu Focal) Importance: Undecided Assignee: Khaled El Mously (kmously) Status: In Progress ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: klibc (Ubuntu) ** Description changed: The GCE internal team responsible for gVNIC would like to have driver updates backported for both Ubuntu 18.04 LTS and Ubuntu 20.04 LTS. + + + [Impact] + Missing functionality from the Google gvnic driver + + + [Test Plan] + Confirm that gvnic module still loads and operates the gvnic driver. More extensive testing done by the gvnic developers at GCE + + + [Regression potential] + Possible regression in gvnic behaviour or functionality. Changes are confined to the gvnic driver code so regression potential is limited to gvnic only. + + + + List of changes: + + 3712db620c613 gve: DQO: Configure interrupts on device up + a9fd7559a367a gve: Check TX QPL was actually assigned + c69a8892d5836 gve: fix the wrong AdminQ buffer overflow check + f48adc2842b17 gve: DQO: Remove incorrect prefetch + 98fd04939ae7e gve: Simplify code and axe the use of a deprecated API + 56c0904d8491d gve: Propagate error codes to caller + 86cd2b58d1e63 gve: DQO: Fix off by one in gve_rx_dqo() + ea364622fb118 gve: Fix warnings reported for DQO patchset + 8890e8783c6e6 gve: DQO: Add RX path + abfc55f80d423 gve: DQO: Add TX path + ef63867982913 gve: DQO: Add ring allocation and initialization + dc3e0aef11bf0 gve: DQO: Add core netdev features + 873fd9825efd7 gve: Update adminq commands to support DQO queues + 543dc0e670472 gve: Add DQO fields for core data structures + b580730931348 gve: Add dqo descriptors + 74e123d3c62b2 gve: Add support for DQO RX PTYPE map + a9a3bfdd5f679 gve: adminq: DQO specific device descriptor logic + 3e6d068c103f8 gve: Introduce per netdev `enum gve_queue_format` + a6b09c93c1735 gve: Introduce a new model for device options + 34d6b75678979 gve: Add support for raw addressing in the tx path + 30b6221596699 Revert "gve: Check TX QPL was actually assigned" + 98478993bb3f9 gve: Make gve_rx_slot_page_info.page_offset an absolute offset + ff4b20bb7e5f4 gve: gve_rx_copy: Move padding to an argument + 5fc5c482008b5 gve: Move some static functions to a common file + ed1e0daeee1ac gve:
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
Patch proposed upstream: https://lists.zytor.com/archives/klibc/2021-December/004629.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
(updated the bug description with further details according to the SRU
template, including reproduction steps)
** Description changed:
** SRU TEMPLATE DRAFT **
[Impact]
+ In some cases, ipconfig can take a longer time than the user-specified
timeouts, causing unexpected delays.
+
+ [Test Plan]
+ Any situation where ipconfig encounters an error sending the DHCP packet, it
will automatically set a delay of 10 seconds, which could be longer than the
user-specified timeout. It can be reproduced by creating a dummy interface and
attempting to run ipconfig on it with a timeout value of less than 10:
+
+ # ip link add eth1 type dummy
+ # date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
+ Thu Nov 18 04:46:13 EST 2021
+ IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
+ IP-Config: no response after 2 secs - giving up
+ Thu Nov 18 04:46:23 EST 2021
- [Test Plan]
+ ^ Notice above, ipconfig thinks that it waited 2 seconds, but the
+ timestamps show an actual delay of 10 seconds.
[Where problems could occur]
+ Please see reproduction steps above. We are seeing this in production too
(see comment #2).
[Other Info]
+ A patch to fix the issue is being proposed here. It is a safe fix - it only
checks before going into sleep that the timeout never exceeds the
user-requested value.
[Original Description]
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again later"
at time equal now + 10 seconds by setting
s->expire = now + 10;
This can happen at any time during the main event loop, which can end up
extending the user-specified timeout if "now + 10" is greater than
"start_time + user-specified-timeout".
I believe a patch like the following is needed to avoid this problem:
--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)
if (timeout > s->expire - now.tv_sec)
timeout = s->expire - now.tv_sec;
+
+ /* Compensate for already-lost time */
+ gettimeofday(, NULL);
+ if (now.tv_sec + timeout > start + loop_timeout) {
+ timeout = loop_timeout - (now.tv_sec - start);
+ printf("Lowered timeout to match user request
= (%d s) \n", timeout);
+ }
}
I believe the current behaviour is buggy. This is confirmed when the
following line is executed:
if (loop_timeout >= 0 &&
now.tv_sec - start >= loop_timeout) {
printf("IP-Config: no response after %d "
"secs - giving up\n", loop_timeout);
rc = -1;
goto bail;
}
'loop_timeout' is the user-specified time-out. With a value of 2, in
case of error, this line prints:
IP-Config: no response after 2 secs - giving up
So it thinks that it waited 2 seconds - however, in reality it had
actually waited for 10 seconds.
The suggested code-change ensures that the timeout that is actually used
never exceeds the user-specified timeout.
** Description changed:
- ** SRU TEMPLATE DRAFT **
[Impact]
In some cases, ipconfig can take a longer time than the user-specified
timeouts, causing unexpected delays.
[Test Plan]
Any situation where ipconfig encounters an error sending the DHCP packet, it
will automatically set a delay of 10 seconds, which could be longer than the
user-specified timeout. It can be reproduced by creating a dummy interface and
attempting to run ipconfig on it with a timeout value of less than 10:
# ip link add eth1 type dummy
# date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
Thu Nov 18 04:46:13 EST 2021
IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
IP-Config: no response after 2 secs - giving up
Thu Nov 18 04:46:23 EST 2021
-
^ Notice above, ipconfig thinks that it waited 2 seconds, but the
timestamps show an actual delay of 10 seconds.
-
[Where problems could occur]
Please see reproduction steps above. We are seeing this in production too
(see comment #2).
-
[Other Info]
A patch to fix the issue is being proposed here. It is a safe fix - it only
checks before going into sleep that the timeout never exceeds the
user-requested value.
-
[Original Description]
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
Hello @Eric. > What make Bionic more susceptible to this particular problem ? Bionic kernel version in use ? else ? I believe klibc/ipconfig itself is susceptible to the problem in Bionic and Focal and elsewhere. However, Focal (which uses klibc 2.0.7) uses dhclient for networking initialization instead of ipconfig, therefore I am not really concerned about fixing the ipconfig issue in Focal since it is not causing any noticeable problems. I have checked the HEAD of the klibc project and it appears that ipconfig is still susceptible to the timeout problem. Sure I can propose the patch upstream if you like - however, even if they accept it I believe we will still need to apply it separately for Bionic because I do not expect that Bionic will receive any major updates for klibc, so it will not get any upstream fixes. It will remain on 2.0.4 as far as I know. It is currently version 2.0.4-9ubuntu2 in Bionic which means we are carrying (2?) Ubuntu-specific patches on top of 2.0.4. I believe this fix can be added as well to produce 2.0.4-9ubuntu3. I will attempt to upstream this fix to klibc, but I believe the change to Bionic should happen in parallel/independently since the upstream patch will not make its way back to Bionic (which is stuck at 2.0.4, as mentioned above). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
Hi @Eric - thanks for the follow-up and sorry for the delayed reply. > I don't see this piece of code in the klibc upstream project[0] Are you referring to the piece of code that I am suggesting as a fix? If so, it makes sense that it doesn't exist elsewhere, which is why I am suggesting it be incorporated into klibc. I have checked upstream klibc 2.0.4 which is the version that Bionic uses and it applies cleanly there. I am not sure that it would help us to get the fix upstreamed in a new version of klibc since the problem is only affecting Bionic, and Bionic uses klibc 2.0.4 + some Ubuntu changes. I assumed we can just add the additional fix as another Ubuntu-specific change on top ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
For some background info, this issue is affecting one of the instance types of a cloud partner. The instance has 18 physical ethernet interfaces (bonded), but only one of which has a media connection. On boot-up, ipconfig is called to do DHCP for all 18 devices. 17 of them fail to send a DHCP request (because no media is connected), and so each one ends up taking 10 seconds, even though the user-specified timeout for each interface was only 2. This delays the entire boot-up sequence by about 3 minutes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
Adding a debdiff of the patch as well. I am not sure if I generated it correctly though.. ** Patch added: "Suggested patch that fixes the problem" https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+attachment/5532730/+files/honour-user-requested-timeouts-in-all-cases.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
** Description changed:
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again later"
at time equal now + 10 seconds by setting
s->expire = now + 10;
-
- This can happen at any time during the main event loop, which can end up
extending the user-specified timeout if "now + 10" is greater than "start_time
+ user-specified-timeout".
+ This can happen at any time during the main event loop, which can end up
+ extending the user-specified timeout if "now + 10" is greater than
+ "start_time + user-specified-timeout".
I believe a patch like the following is needed to avoid this problem:
--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)
- if (timeout > s->expire - now.tv_sec)
- timeout = s->expire - now.tv_sec;
+ if (timeout > s->expire - now.tv_sec)
+ timeout = s->expire - now.tv_sec;
+
+ /* Compensate for already-lost time */
+ gettimeofday(, NULL);
+ if (now.tv_sec + timeout > start + loop_timeout) {
+ timeout = loop_timeout - (now.tv_sec - start);
+ printf("Lowered timeout to match user request
= (%d s) \n", timeout);
+ }
- }
+ }
+
+
+ I believe the current behaviour is buggy. This is confirmed when the
following line is executed:
+
+
+ if (loop_timeout >= 0 &&
+ now.tv_sec - start >= loop_timeout) {
+ printf("IP-Config: no response after %d "
+"secs - giving up\n", loop_timeout);
+ rc = -1;
+ goto bail;
+ }
+
+
+ 'loop_timeout' is the user-specified time-out. With a value of 2, in case of
error, this line prints:
+
+ IP-Config: no response after 2 secs - giving up
+
+
+ So it thinks that it waited 2 seconds - however, in reality it had actually
waited for 10 seconds.
+
+ The suggested code-change ensures that the timeout that is actually used
+ never exceeds the user-specified timeout.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does not honour user-requested timeouts in some cases
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] [NEW] ipconfig does not honour user-requested timeouts in some cases
Public bug reported:
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again later"
at time equal now + 10 seconds by setting
s->expire = now + 10;
This can happen at any time during the main event loop, which can end up
extending the user-specified timeout if "now + 10" is greater than "start_time
+ user-specified-timeout".
I believe a patch like the following is needed to avoid this problem:
--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)
if (timeout > s->expire - now.tv_sec)
timeout = s->expire - now.tv_sec;
+
+ /* Compensate for already-lost time */
+ gettimeofday(, NULL);
+ if (now.tv_sec + timeout > start + loop_timeout) {
+ timeout = loop_timeout - (now.tv_sec - start);
+ printf("Lowered timeout to match user request =
(%d s) \n", timeout);
+ }
}
** Affects: klibc (Ubuntu)
Importance: Undecided
Status: New
** Affects: klibc (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: klibc (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does not honour user-requested timeouts in some cases
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940261] Re: ubuntu_seccomp 11-basic-basic_errors failure on X/oracle
Found on: 2021.09.27/bionic/linux-gcp-4.15/4.15.0-1110.124 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940261 Title: ubuntu_seccomp 11-basic-basic_errors failure on X/oracle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1940261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945559] Re: Failed to start Kernel Modules and small Ubuntu resolution
@Muhammed: It may be a good idea also to try a fresh Ubuntu 18.04 installation inside a different VM (with the same exact settings as this one) to see if it has the same issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945559 Title: Failed to start Kernel Modules and small Ubuntu resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943902] Re: NVME errors in confidential vms
** Description changed: See https://canonical.lightning.force.com/lightning/r/Case/5004K09WBzrQAG/view for more info [Impact] Using nvme with swiotlb in confidential VMs can encounter hardware read/write errors. [Fix] - The following upstream patches address this: + The following upstream patches from v5.12 address this: 3d2d861eb03e nvme-pci: set min_align_mask 1f221a0d0dbf swiotlb: respect min_align_mask 16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single 26a7e094783d swiotlb: refactor swiotlb_tbl_map_single ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single c32a77fd1878 swiotlb: factor out a nr_slots helper c7fbeca757fe swiotlb: factor out an io_tlb_offset helper b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define [Test] Using a confidential VM, with 'swiotlb=force' set on the kernel command line, and an additional nvme device attached: $ sudo mkfs.xfs -f /dev/nvme2n1 meta-data=/dev/nvme2n1 isize=512agcount=4, agsize=131072 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, refl ink=0 data = bsize=4096 blocks=524288, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=2560, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 mkfs.xfs: pwrite failed: Input/output error Note the input/output error The error no longer happens with the fixes applied. [Regression Potential] Low risk as the patches are mostly clean-up and refactor. Regression in swiotlb could cause hardware read/write errors -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943902 Title: NVME errors in confidential vms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1943902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943902] Re: NVME errors in confidential vms
** Description changed: See https://canonical.lightning.force.com/lightning/r/Case/5004K09WBzrQAG/view for more info [Impact] - Using nvme hardware that uses swiotlb in confidential VMs can encounter hardware read/write errors. - + Using nvme hardware that uses in confidential VMs can encounter hardware read/write errors. [Fix] The following upstream patches address this: 3d2d861eb03e nvme-pci: set min_align_mask 1f221a0d0dbf swiotlb: respect min_align_mask 16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single 26a7e094783d swiotlb: refactor swiotlb_tbl_map_single ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single c32a77fd1878 swiotlb: factor out a nr_slots helper c7fbeca757fe swiotlb: factor out an io_tlb_offset helper b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define - [Test] Using a confidential VM, with 'swiotlb=force' set on the kernel command - line, and an additional swiotlb nvme device attached: + line, and an additional nvme device attached: - $ sudo mkfs.xfs -f /dev/nvme2n1 - meta-data=/dev/nvme2n1 isize=512agcount=4, agsize=131072 blks - = sectsz=512 attr=2, projid32bit=1 - = crc=1finobt=1, sparse=0, rmapbt=0, refl - ink=0 - data = bsize=4096 blocks=524288, imaxpct=25 - = sunit=0 swidth=0 blks - naming =version 2 bsize=4096 ascii-ci=0 ftype=1 - log =internal log bsize=4096 blocks=2560, version=2 - = sectsz=512 sunit=0 blks, lazy-count=1 - realtime =none extsz=4096 blocks=0, rtextents=0 + $ sudo mkfs.xfs -f /dev/nvme2n1 + meta-data=/dev/nvme2n1 isize=512agcount=4, agsize=131072 blks + = sectsz=512 attr=2, projid32bit=1 + = crc=1finobt=1, sparse=0, rmapbt=0, refl + ink=0 + data = bsize=4096 blocks=524288, imaxpct=25 + = sunit=0 swidth=0 blks + naming =version 2 bsize=4096 ascii-ci=0 ftype=1 + log =internal log bsize=4096 blocks=2560, version=2 + = sectsz=512 sunit=0 blks, lazy-count=1 + realtime =none extsz=4096 blocks=0, rtextents=0 mkfs.xfs: pwrite failed: Input/output error - Note the input/output error The error no longer happens with the fixes applied. + [Regression Potential] + + Low risk as the patches are mostly clean-up and refactor. + Regression in swiotlb could cause hardware read/write errors ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oracle (Ubuntu) ** Also affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-gcp-5.4 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-gcp-5.4 (Ubuntu Focal) ** No longer affects: linux-gcp (Ubuntu Bionic) ** Changed in: linux-gcp (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp-5.4 (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu Focal) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp-5.4 (Ubuntu Bionic) Assignee: (unassigned) => Khaled El Mously (kmously) ** Description changed: See https://canonical.lightning.force.com/lightning/r/Case/5004K09WBzrQAG/view for more info [Impact] - Using nvme hardware that uses in confidential VMs can encounter hardware read/write errors. + Using nvme with swiotlb in confidential VMs can encounter hardware read/write errors. [Fix] The following upstream patches address this: 3d2d861eb03e nvme-pci: set min_align_mask 1f221a0d0dbf swiotlb: respect min_align_mask 16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single 26a7e094783d swiotlb: refactor swiotlb_tbl_map_single ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single c32a77fd1878 swiotlb: factor out a nr_slots helper c7fbeca757fe swiotlb: factor out an io_tlb_offset helper b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define [Test] Using a confidential VM, with 'swiotlb=force' set on the kernel command line, and an additional nvme device attached: $ sudo mkfs.xfs -f /dev/nvme2n1 meta-data=/dev/nvme2n1 isize=512agcount=4, agsize=131072 blks = sectsz=512 attr=2, p
[Bug 1943902] [NEW] NVME errors in confidential vms
Public bug reported: See https://canonical.lightning.force.com/lightning/r/Case/5004K09WBzrQAG/view for more info [Impact] Using nvme hardware that uses swiotlb in confidential VMs can encounter hardware read/write errors. [Fix] The following upstream patches address this: 3d2d861eb03e nvme-pci: set min_align_mask 1f221a0d0dbf swiotlb: respect min_align_mask 16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single 26a7e094783d swiotlb: refactor swiotlb_tbl_map_single ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single c32a77fd1878 swiotlb: factor out a nr_slots helper c7fbeca757fe swiotlb: factor out an io_tlb_offset helper b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define [Test] Using a confidential VM, with 'swiotlb=force' set on the kernel command line, and an additional swiotlb nvme device attached: $ sudo mkfs.xfs -f /dev/nvme2n1 meta-data=/dev/nvme2n1 isize=512agcount=4, agsize=131072 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, refl ink=0 data = bsize=4096 blocks=524288, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=2560, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 mkfs.xfs: pwrite failed: Input/output error Note the input/output error The error no longer happens with the fixes applied. [Regression Potential] ** Affects: linux-oracle (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943902 Title: NVME errors in confidential vms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1943902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925421] Re: arm64 support
** Tags removed: verification-needed-groovy verification-needed-hirsute ** Tags added: verification-done-groovy verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925421 Title: arm64 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1925421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840488] Re: Disable Bluetooth in cloud kernels
** Tags removed: verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-focal verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840488 Title: Disable Bluetooth in cloud kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1840488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938976] [NEW] linux-gke: Do not build/ship aufs.ko
Public bug reported: See https://partnerissuetracker.corp.google.com/issues/194431474 for more information [Impact] aufs.ko to be removed [Fix] Set CONFIG_AUFS_FS to N. [Test] Confirm that aufs.ko no longer being built. [Regression Potential] No expected regression (aufs functionality will be disabled) ** Affects: linux-gke (Ubuntu) Importance: Undecided Assignee: Khaled El Mously (kmously) Status: In Progress ** Affects: linux-gke-5.4 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gke-5.4 (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux-gke (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oracle (Ubuntu) ** Changed in: linux-gke (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gke (Ubuntu) Status: New => In Progress ** Description changed: See https://partnerissuetracker.corp.google.com/issues/194431474 for more information + + [Impact] + aufs.ko to be removed + + [Fix] + Set CONFIG_AUFS_FS to N. + + [Test] + Confirm that aufs.ko no longer being built. + + [Regression Potential] + No expected regression (aufs functionality will be disabled) ** Also affects: linux-gke (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gke (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-gke-5.4 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-gke-5.4 (Ubuntu Focal) ** No longer affects: linux-gke (Ubuntu Bionic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938976 Title: linux-gke: Do not build/ship aufs.ko To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1938976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928686] Re: Oracle kernel has Android related config options disabled
** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Oracle kernel has Android related config options disabled + Some cloud kernels have Android related config options disabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928686 Title: Some cloud kernels have Android related config options disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1928686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840488] Re: Disable Bluetooth in cloud kernels
** No longer affects: linux-gke-4.15 (Ubuntu Focal) ** No longer affects: linux-gke-4.15 (Ubuntu Eoan) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840488 Title: Disable Bluetooth in cloud kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1840488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840488] Re: Disable Bluetooth in cloud kernels
** Also affects: linux-aws (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gke-4.15 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gke-5.0 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-gke-4.15 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-gke-5.0 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-gke-4.15 (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-gke-5.0 (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840488 Title: Disable Bluetooth in cloud kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1840488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931254] Re: Google Confidential Compute fails to boot with 1.47
** Description changed: # Overview Hirsute and Impish daily builds are currently not booting on Google Confidential Compute. Confidential compute is Google's platform that enables the use of Secure Encrypted Virtualization extension via AMD EPYC CPUs. Booting an image with version 1.45 works, but once upgraded to 1.47, the VM no longer boots, and instead the kernel panics. Launching the image with secure boot, but without confidential compute works as expected. # Expected result The system is able to reboot after the upgrade. # Actual result Kernel panic: https://paste.ubuntu.com/p/mHrvVc6qBc/ # Steps to reproduce Launch a VM in GCE with confidential compute enabled with a serial v20210511a or later and look at the serial log for the kernel panic. Example CLI command to launch a VM: $ gcloud beta compute instances create $USER-confidential-testing --zone =us-west1-b --machine-type=n2d-standard-2 --image=daily-ubuntu-2104 -hirsute-v20210511a --image-project=ubuntu-os-cloud-devel --confidential-compute --maintenance-policy=TERMINATE The last known good working image is daily- ubuntu-2104-hirsute-v20210510. The upgrade that fails is when shim signed is updated from 1.46+15.4-0ubuntu1 to 1.47+15.4-0ubuntu2 # Logs & notes * 20210510 manifest (good): https://paste.ubuntu.com/p/QjnMPcJj7G/ * 20210511a manifest (bad): https://paste.ubuntu.com/p/PvJQwRXHcG/ * diff between manifests: https://paste.ubuntu.com/p/4nJtGxqGn7/ * serial logs of failed boot: https://paste.ubuntu.com/p/mHrvVc6qBc/ # Cause: shim changed the memory type for pages reserved for EFI runtime services, from EfiRuntimeServicesData to EfiBootServicesData. Memory reserved for EFI runtime/boot services must be remapped as encrypted in the kernel (during boot) if SEV (secure encrypted virtualization) is enabled. The original kernel implementation of ioremap only correctly mapped the region as encrypted for EfiRuntimeServicesData regions, so when shim changed the type to EfiBootServicesData the kernel bug was exposed Note that this affects all 5.11 kernels not just gcp. It is possible that gcp is the only cloud that uses sev currently (for "Confidential Computing"). # Fix: Both EfiRuntimeServicesData and EfiBootServicesData must be mapped as encrypted if SEV is active, as per: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8d651ee9c71bb12fc0c8eb2786b66cbe5aa3e43b + + # Test + + Without the fix applied, confirmed that I was able to reproduce the issue described here (complete failure to boot, kernel panic) + With fix, confirmed no issues booting + # Regression potential The fix could potentially cause boot failures, if a memory region is marked encrypted when it shouldn't be. I assume in that case it would cause a panic similar to the one seen here for this bug: general protection fault, probably for non-canonical address 0x314836c31124d346: [#1] SMP NOPTI ** Summary changed: - Google Confidential Compute fails to boot with 1.47 + Google Confidential Compute fails to boot with shim version 1.47 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931254 Title: Google Confidential Compute fails to boot with shim version 1.47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931254] Re: Google Confidential Compute fails to boot with 1.47
gression potential The fix could potentially cause boot failures, if a memory region is marked encrypted when it isn't. I assume it would cause a panic similar to the one seen here for this bug: general protection fault, probably for non-canonical address 0x314836c31124d346: [#1] SMP NOPTI ** Description changed: # Overview Hirsute and Impish daily builds are currently not booting on Google Confidential Compute. Confidential compute is Google's platform that enables the use of Secure Encrypted Virtualization extension via AMD EPYC CPUs. Booting an image with version 1.45 works, but once upgraded to 1.47, the VM no longer boots, and instead the kernel panics. Launching the image with secure boot, but without confidential compute works as expected. # Expected result The system is able to reboot after the upgrade. # Actual result Kernel panic: https://paste.ubuntu.com/p/mHrvVc6qBc/ # Steps to reproduce Launch a VM in GCE with confidential compute enabled with a serial v20210511a or later and look at the serial log for the kernel panic. Example CLI command to launch a VM: $ gcloud beta compute instances create $USER-confidential-testing --zone =us-west1-b --machine-type=n2d-standard-2 --image=daily-ubuntu-2104 -hirsute-v20210511a --image-project=ubuntu-os-cloud-devel --confidential-compute --maintenance-policy=TERMINATE The last known good working image is daily- ubuntu-2104-hirsute-v20210510. The upgrade that fails is when shim signed is updated from 1.46+15.4-0ubuntu1 to 1.47+15.4-0ubuntu2 # Logs & notes * 20210510 manifest (good): https://paste.ubuntu.com/p/QjnMPcJj7G/ * 20210511a manifest (bad): https://paste.ubuntu.com/p/PvJQwRXHcG/ * diff between manifests: https://paste.ubuntu.com/p/4nJtGxqGn7/ * serial logs of failed boot: https://paste.ubuntu.com/p/mHrvVc6qBc/ # Cause: shim changed the memory type for pages reserved for EFI runtime services, from EfiRuntimeServicesData to EfiBootServicesData. Memory reserved for EFI runtime/boot services must be remapped as encrypted in the kernel (during boot) if SEV (secure encrypted virtualization) is enabled. The original kernel implementation of ioremap only correctly mapped the region as encrypted for EfiRuntimeServicesData regions, so when shim changed the type to EfiBootServicesData the kernel bug was exposed # Fix: Both EfiRuntimeServicesData and EfiBootServicesData must be mapped as encrypted if SEV is active, as per: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8d651ee9c71bb12fc0c8eb2786b66cbe5aa3e43b # Regression potential The fix could potentially cause boot failures, if a memory region is - marked encrypted when it isn't. I assume it would cause a panic similar - to the one seen here for this bug: + marked encrypted when it shouldn't be. I assume in that case it would + cause a panic similar to the one seen here for this bug: general protection fault, probably for non-canonical address 0x314836c31124d346: [#1] SMP NOPTI ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-gcp (Ubuntu) ** No longer affects: linux-gcp (Ubuntu Hirsute) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Description changed: # Overview Hirsute and Impish daily builds are currently not booting on Google Confidential Compute. Confidential compute is Google's platform that enables the use of Secure Encrypted Virtualization extension via AMD EPYC CPUs. Booting an image with version 1.45 works, but once upgraded to 1.47, the VM no longer boots, and instead the kernel panics. Launching the image with secure boot, but without confidential compute works as expected. # Expected result The system is able to reboot after the upgrade. # Actual result Kernel panic: https://paste.ubuntu.com/p/mHrvVc6qBc/ # Steps to reproduce Launch a VM in GCE with confidential compute enabled with a serial v20210511a or later and look at the serial log for the kernel panic. Example CLI command to launch a VM: $ gcloud beta compute instances create $USER-confidential-testing --zone =us-west1-b --machine-type=n2d-standard-2 --image=daily-ubuntu-2104 -hirsute-v20210511a --image-project=ubuntu-os-cloud-devel --confidential-compute --maintenance-policy=TERMINATE The last known good working image is daily- ubuntu-2104-hirsute-v20210510. The upgrade that fails is when shim signed is updated from 1.46+15.4-0ubuntu1 to 1.47+15.4-0ubuntu2 # Logs & notes * 20210510 manifest (good)
[Bug 1931254] Re: Google Confidential Compute fails to boot with 1.47
** Also affects: linux-gcp (Ubuntu Hirsute) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931254 Title: Google Confidential Compute fails to boot with 1.47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1931254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931254] Re: Google Confidential Compute fails to boot with 1.47
@Peter Gonda -- You seem to be 100% correct. Thank you for the helpful pointer! I have confirmed the fix and shim-side of the changes that exposed the issue. I will SRU the fix asap. ** No longer affects: shim-signed (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931254 Title: Google Confidential Compute fails to boot with 1.47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1931254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927682] Re: netfilter: x_tables: fix compat match/target pad out-of-bound write
** Also affects: linux-5.4 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-5.4 (Ubuntu Focal) ** No longer affects: linux-5.4 (Ubuntu Groovy) ** No longer affects: linux-5.4 (Ubuntu Hirsute) ** Changed in: linux-5.4 (Ubuntu Bionic) Status: New => Fix Released ** No longer affects: linux (Ubuntu Bionic) ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927682 Title: netfilter: x_tables: fix compat match/target pad out-of-bound write To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928686] Re: Oracle kernel has Android related config options disabled
In 4.15, CONFIG_ASHMEM and CONFIG_ANDROID_BINDER_IPC can only be compiled as =y (not =m) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928686 Title: Oracle kernel has Android related config options disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1928686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928686] Re: Oracle kernel has Android related config options disabled
@Simon, is this needed in the 4.15 kernel? ** No longer affects: linux-oracle (Ubuntu Impish) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928686 Title: Oracle kernel has Android related config options disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1928686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928686] Re: Oracle kernel has Android related config options disabled
** Also affects: linux-oracle (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Impish) Importance: Undecided Status: Confirmed ** Also affects: linux-oracle (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928686 Title: Oracle kernel has Android related config options disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1928686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931959] [NEW] iscsi-related backports requested for Oracle-cloud
Public bug reported: As part of some work to enable high performance iscsi storage leveraging multipath, Oracle submitted and landed patches upstream, which were released as part of 5.10. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2a242d59d6b908341c0d426bc6e7f8e28871cbd0 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0610959fbbca62b534f1f276873fd297f76b164b commit 2a242d59d6b908341c0d426bc6e7f8e28871cbd0 Author: Mike Christie michael.chris...@oracle.com Date: Thu Oct 1 10:35:53 2020 -0500 scsi: core: Add limitless cmd retry support commit 0610959fbbca62b534f1f276873fd297f76b164b Author: Mike Christie michael.chris...@oracle.com Date: Thu Oct 1 10:35:54 2020 -0500 scsi: sd: Allow user to configure command retries See https://canonical.lightning.force.com/lightning/r/Case/5004K05pykQQAQ/view for more info. [Impact] Optimizations/improvements in iscsi-code [Fix] 2 patches - see above [Test] Build, boot, initiate an iscsi connection to a target. [Regression Potential] Possible impact on iscsi functionality. ** Affects: linux-oracle (Ubuntu) Importance: Undecided Assignee: Khaled El Mously (kmously) Status: New ** Affects: linux-oracle (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux-oracle (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931959 Title: iscsi-related backports requested for Oracle-cloud To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1931959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic
Thanks for the extensive testing, Mariusz. (I assume -137 doesn't have the performance problem?) So, for comment #9 - the difference in loaded modules comes down to 20 additional modules that were loaded when performance was bad: -ip6_tables 28672 0 -iptable_filter 16384 0 -ip_tables 28672 1 iptable_filter -x_tables 40960 3 iptable_filter,ip6_tables,ip_tables -tcp_diag 16384 0 -udp_diag 16384 0 -inet_diag 24576 2 tcp_diag,udp_diag -cpuid 16384 0 -btrfs 1155072 0 -zstd_compress 163840 1 btrfs -xor 24576 1 btrfs -raid6_pq 114688 1 btrfs -ufs 77824 0 -qnx4 16384 0 -minix 32768 0 -ntfs 102400 0 -msdos 20480 0 -jfs 188416 0 -xfs 1204224 0 -libcrc32c 16384 1 xfs Seems they are mostly filesystem modules and iptables modules. It is possible that this could affect performance - though unlikely to cause performance issues simply by them being loaded. If they are causing the performance hit it would probably mean that some thing else is running not just additional modules loaded in memory. So, if I understand correctly, -140 seemed initially fine, but after some time, performance degrades. That makes things a bit more interesting. Do you see those additional modules loaded when performance is degraded? Note that all those additional modules don't seem to have any external dependencies other than themselves - they depend only on each other. So it should be easily possible to unload them and see if that "fixes" the performance issue. By the way, kernels -143 and -144 have been released since this bug was created. Maybe it is worthwhile to also try those kernels? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928744 Title: Disk IO very slow on kernel 4.15.0-142-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929920] [NEW] 'sudo' commands fail with "already defined" errors on oracle images
Public bug reported: The problem was first noticed when it caused these errors: http://10.246.72.9/5.11.0-1007.7-oracle/hirsute-linux-oracle-oracle- amd64-5.11.0-VM.Standard2.1-ubuntu_qrt_kernel_security/ubuntu_qrt_kernel_security/results/ubuntu_qrt_kernel_security .test-kernel-security.py/debug/ubuntu_qrt_kernel_security.test-kernel- security.py.DEBUG.html and Sam has narrowed it down to a problem running sudo commands, which all fail with the error: Alias "x" already defined This affects the 2021-05-10 SRU cycle. More info on this Trello card: https://trello.com/c/dZXTo7L3/1257-alias-x-already-defined-error- triggered-by-sudo-in-oracle-hirsute ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: sru-20210510 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: kernel-sru-workflow ** Tags added: sru-20210510 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929920 Title: 'sudo' commands fail with "already defined" errors on oracle images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927050] Re: Enable BLK_DEV_NVME =y to support "shielded VM minimal images"
** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-groovy ** Tags added: verification-done-bionic verification-done-focal verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927050 Title: Enable BLK_DEV_NVME =y to support "shielded VM minimal images" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1927050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic
Hi @Mariusz - thank you for the bug report. That certainly sounds like a kernel bug based on your description. Doing a kernel bisect is probably the fastest approach to identifying the offending change. There are 392 changes between -136 and -142 so it could take up to 9 tests for a full bisect. @Mariusz, is it possible to find out which (if any) of the intermediate kernels between -136 and -142 are affected ? If you don't have any of the intermediate kernels installed already, you can install them with a command like this one: sudo apt-get install linux-image-4.15.0-137-generic linux- headers-4.15.0-137-generic linux-modules-4.15.0-137-generic linux- modules-extra-4.15.0-137-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928744 Title: Disk IO very slow on kernel 4.15.0-142-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928021] [NEW] ubuntu_sysdig_smoke_test: "test_060_nx" fails on focal/linux-oracle
Public bug reported: Example failure: http://10.246.72.9/5.4.0-1045.49-oracle/focal-linux-oracle-oracle- amd64-5.4.0-VM.Standard2.1-ubuntu_qrt_kernel_security/ubuntu_qrt_kernel_security/results/ubuntu_qrt_kernel_security .test-kernel-security.py/debug/ubuntu_qrt_kernel_security.test-kernel- security.py.DEBUG.html Failure output: 585.FAIL: test_060_nx (__main__.KernelSecurityTest) 586.NX bit is working 587.-- 588.Traceback (most recent call last): 589.File "./test-kernel-security.py", line 554, in test_060_nx 590.self.assertShellExitEquals(rie_expected, ["./nx-test-rie", "data"]) 591.File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1166, in assertShellExitEquals 592.self.assertEqual(expected, rc, msg + result + report) 593.AssertionError: Got exit code -11, expected 0 594.Command: './nx-test-rie', 'data' 595.Output: 596.rodata:0x559730ee5008 597.data: 0x559730ee7010 598.bss: 0x559730ef7040 599.brk: 0x5597313a62b0 600.rw: 0x7fa963894000 601.rwx: 0x7fa963867000 602.stack: 0x7ffe099e9eb0 603.Dump of /proc/self/maps: 604.559730ee3000-559730ee4000 r--p 08:01 1562993 /home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test-rie 605.559730ee4000-559730ee5000 r-xp 1000 08:01 1562993 /home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test-rie 606.559730ee5000-559730ee6000 r--p 2000 08:01 1562993 /home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test-rie 607.559730ee6000-559730ee7000 r--p 2000 08:01 1562993 /home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test-rie 608.559730ee7000-559730ee8000 rw-p 3000 08:01 1562993 /home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test-rie 609.559730ee8000-559730ef8000 rw-p 00:00 0 610.5597313a5000-5597313c6000 rw-p 00:00 0 [heap] 611.7fa96366b000-7fa96369 r--p 08:01 45790 /usr/lib/x86_64-linux-gnu/libc-2.31.so 612.7fa96369-7fa963808000 r-xp 00025000 08:01 45790 /usr/lib/x86_64-linux-gnu/libc-2.31.so 613.7fa963808000-7fa963852000 r--p 0019d000 08:01 45790 /usr/lib/x86_64-linux-gnu/libc-2.31.so 614.7fa963852000-7fa963853000 ---p 001e7000 08:01 45790 /usr/lib/x86_64-linux-gnu/libc-2.31.so 615.7fa963853000-7fa963856000 r--p 001e7000 08:01 45790 /usr/lib/x86_64-linux-gnu/libc-2.31.so 616.7fa963856000-7fa963859000 rw-p 001ea000 08:01 45790 /usr/lib/x86_64-linux-gnu/libc-2.31.so 617.7fa963859000-7fa96385f000 rw-p 00:00 0 618.7fa963867000-7fa963868000 rwxp 00:00 0 619.7fa963868000-7fa963869000 r--p 08:01 45783 /usr/lib/x86_64-linux-gnu/ld-2.31.so 620.7fa963869000-7fa96388c000 r-xp 1000 08:01 45783 /usr/lib/x86_64-linux-gnu/ld-2.31.so 621.7fa96388c000-7fa963894000 r--p 00024000 08:01 45783 /usr/lib/x86_64-linux-gnu/ld-2.31.so 622.7fa963894000-7fa963895000 rw-p 00:00 0 623.7fa963895000-7fa963896000 r--p 0002c000 08:01 45783 /usr/lib/x86_64-linux-gnu/ld-2.31.so 624.7fa963896000-7fa963897000 rw-p 0002d000 08:01 45783 /usr/lib/x86_64-linux-gnu/ld-2.31.so 625.7fa963897000-7fa963898000 rw-p 00:00 0 626.7ffe099cb000-7ffe099ec000 rwxp 00:00 0 [stack] 627.7ffe099ee000-7ffe099f1000 r--p 00:00 0 [vvar] 628.7ffe099f1000-7ffe099f2000 r-xp 00:00 0 [vdso] 629.ff60-ff601000 --xp 00:00 0 [vsyscall] 630.Attempting to execute function at 0x559730ee7010 631.If this program seg-faults, the region was enforced as non-executable... 632. 633. 634.-- 635.Ran 125 tests in 73.445s 636. 637.FAILED (failures=1) This failure is expected on the 5.4 oracle kernel, since it no longer assumes READ_IMPLIES_EXEC personality by default, as per this change: https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux- oracle/+git/focal/commit/?id=0e74912698dc008056759c501e7de3c551daedf1 So this test will fail from now on on f/oracle. The test should treat f/oracle as it treats the 5.8 kernels - it should expect a return output of -11 not 0. ** Affects: qa-regression-testing Importance: Undecided Status: New ** Also affects: qa-regression-testing Importance: Undecided Status: New ** No longer affects: linux-oracle (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928021
[Bug 1927682] Re: netfilter: x_tables: fix compat match/target pad out-of-bound write
** Description changed: This issue: https://github.com/torvalds/linux/commit/b29c457a6511435960115c0f548c4360d5f4801d + + + [Impact] + Data corruption and/or leak. + + [Fix] + Zero out entire data structure beforehand + + + [Test] + Boot-test only so far. + + [Regression Potential] + Possible effect on iptables/nftables. Though considered minimal risk as the patch has only a very localized effect and is accepted upstream in v5.12 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: kernel-sru-workflow ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927682 Title: netfilter: x_tables: fix compat match/target pad out-of-bound write To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927050] Re: Enable BLK_DEV_NVME =y to support "shielded VM minimal images"
** Also affects: linux-gcp (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-gcp-4.15 (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux-gcp-4.15 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-gcp (Ubuntu Hirsute) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927050 Title: Enable BLK_DEV_NVME =y to support "shielded VM minimal images" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1927050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927050] Re: Enable BLK_DEV_NVME =y to support "shielded VM minimal images"
** Description changed: This is requested by CPC -- see the title. + + [Impact] + nvme.ko exists outside the kernel currently + + [Fix] + Enable BLK_DEV_NVME=y + + [Test] + Tested by CPC crew / Google: + + > The test images have passed testing and we would like this enabled so we + > can have minimal images boot with NVME boot disk and so we can enable + > GCE confidential VMs with minimal images. + + + [Regression Potential] + Not aware of any. ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Changed in: linux-gcp (Ubuntu) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927050 Title: Enable BLK_DEV_NVME =y to support "shielded VM minimal images" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1927050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927050] [NEW] Enable BLK_DEV_NVME =y to support "shielded VM minimal images"
Public bug reported: This is requested by CPC -- see the title. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927050 Title: Enable BLK_DEV_NVME =y to support "shielded VM minimal images" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925421] Re: arm64 support
** Changed in: linux-oracle (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925421 Title: arm64 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1925421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925421] Re: arm64 support
** Description changed: + See + https://canonical.lightning.force.com/lightning/r/Case/5003z2BzFG4AAN/view + for more info - https://canonical.lightning.force.com/lightning/r/Case/5003z2BzFG4AAN/view + + [Impact] + No support for arm64 currently + + + [Fix] + Add arm64 support, including hardware support patches + + [Test] + Confirm that it boots on desired arm64 hardware, as well as VMs + + [Regression Potential] + This was never working on arm64 so there should be no risk of regression. + The requested changes included some refactorings of early memory initialization code (all arches) so this presents a small risk. The changes were tested on arm64 as well amd64. ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Changed in: linux-oracle (Ubuntu) Status: New => In Progress ** Changed in: linux-oracle (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925421 Title: arm64 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1925421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925421] Re: arm64 support
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oracle (Ubuntu) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925421 Title: arm64 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925421] Re: arm64 support
** Description changed: - Please + + https://canonical.lightning.force.com/lightning/r/Case/5003z2BzFG4AAN/view -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925421 Title: arm64 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1925421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925421] [NEW] arm64 support
Public bug reported: Please ** Affects: linux-oracle (Ubuntu) Importance: Undecided Assignee: Khaled El Mously (kmously) Status: New ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Changed in: linux-oracle (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925421 Title: arm64 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1925421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918668] Re: improper memcg accounting causes NULL pointer derefs
To verify: - I installed groovy on 'durin' (in the maas pod), which installed with kernel -48. - Enabled -proposed, installed the new -49 kernel. (this automatically runs update-grub) - rebooted, confirmed that -49 is running. - ran update-grub manually. No NULL dereferences were observed. Marking as verified. ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918668 Title: improper memcg accounting causes NULL pointer derefs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908264] Re: Disable Atari partition support for cloud kernels
** No longer affects: linux-gke (Ubuntu Hirsute) ** No longer affects: linux-gke (Ubuntu Groovy) ** No longer affects: linux-gke (Ubuntu Bionic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908264 Title: Disable Atari partition support for cloud kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1908264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908264] Re: Disable Atari partition support for cloud kernels
** Also affects: linux-gkeop (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-gkeop (Ubuntu Xenial) ** No longer affects: linux-gkeop (Ubuntu Bionic) ** No longer affects: linux-gkeop (Ubuntu Groovy) ** No longer affects: linux-gkeop (Ubuntu Hirsute) ** No longer affects: linux-oracle (Ubuntu Xenial) ** No longer affects: linux-gke (Ubuntu Xenial) ** No longer affects: linux-gcp (Ubuntu Xenial) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908264 Title: Disable Atari partition support for cloud kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1908264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921825] Re: Kernel panic on `5.4.0-1033-gke` (Kernel panic - not syncing: Aiee, killing interrupt handler!) possibly iscsi related
** Changed in: linux-gke (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921825 Title: Kernel panic on `5.4.0-1033-gke` (Kernel panic - not syncing: Aiee, killing interrupt handler!) possibly iscsi related To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1921825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921825] Re: Kernel panic on `5.4.0-1033-gke` (Kernel panic - not syncing: Aiee, killing interrupt handler!) possibly iscsi related
** Description changed: + [Impact] + Kernel panic during high iscsi activity + + This stacktrace [ 223.386958] BUG: scheduling while atomic: iscsiadm/18136/0x0200 [ 223.393390] Modules linked in: tcp_diag inet_diag xt_nat ipt_REJECT nf_reject_ipv4 xt_tcpudp ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs sch_htb ebt_ip ebtable_filter ebtables veth xt_mark br_netfilter iptable_mangle xt_MASQUERADE xt_comment xt_addrtype iptable_nat binfmt_misc iptable_filter bpfilter xt_conntrack nf_nat bridge stp llc xfrm_user xfrm_algo aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper input_leds serio_raw sch_fq_codel sunrpc ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi virtio_rng ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear psmouse virtio_net net_failover failover [ 223.393429] CPU: 6 PID: 18136 Comm: iscsiadm Kdump: loaded Not tainted 5.4.0-1033-gke #35~18.04.1-Ubuntu [ 223.393430] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [ 223.393430] Call Trace: [ 223.393439] dump_stack+0x6d/0x95 [ 223.393464] __schedule_bug+0x55/0x70 [ 223.393467] __schedule+0x61b/0x710 [ 223.393469] schedule+0x33/0xa0 [ 223.393472] __lock_sock+0x7d/0xc0 [ 223.393475] ? wait_woken+0x80/0x80 [ 223.393477] lock_sock_nested+0x64/0x70 [ 223.393479] inet_getname+0xaa/0xe0 [ 223.393482] kernel_getpeername+0x1b/0x20 [ 223.393485] iscsi_sw_tcp_conn_get_param+0xa6/0x110 [iscsi_tcp] [ 223.393494] show_conn_ep_param_ISCSI_PARAM_CONN_ADDRESS+0x7e/0xa0 [scsi_transport_iscsi] [ 223.393496] dev_attr_show+0x1d/0x50 [ 223.393499] sysfs_kf_seq_show+0xa1/0x110 [ 223.393502] kernfs_seq_show+0x27/0x30 [ 223.393504] seq_read+0xda/0x420 [ 223.393506] kernfs_fop_read+0x141/0x1a0 [ 223.393510] __vfs_read+0x1b/0x40 [ 223.393512] vfs_read+0x8e/0x130 [ 223.393513] ksys_read+0xa7/0xe0 [ 223.393515] __x64_sys_read+0x1a/0x20 [ 223.393518] do_syscall_64+0x57/0x190 [ 223.393521] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 223.393523] RIP: 0033:0x7f45793ce910 [ 223.393525] Code: b6 fe ff ff 48 8d 3d 0f be 08 00 48 83 ec 08 e8 06 db 01 00 66 0f 1f 44 00 00 83 3d f9 2d 2c 00 00 75 10 b8 00 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 31 c3 48 83 ec 08 e8 de 9b 01 00 48 89 04 24 [ 223.393526] RSP: 002b:7ffd9fa13688 EFLAGS: 0246 ORIG_RAX: [ 223.393527] RAX: ffda RBX: 7ffd9fa13820 RCX: 7f45793ce910 [ 223.393528] RDX: 0100 RSI: 7ffd9fa13720 RDI: 0003 [ 223.393528] RBP: 7ffd9fa13720 R08: R09: [ 223.393529] R10: 0064 R11: 0246 R12: 0003 [ 223.393530] R13: 7ffd9fa13c60 R14: 555b0d613708 R15: 555b0d613300 [ 223.393581] sd 1:0:0:0: [sdb] Write Protect is off [ 223.393583] sd 1:0:0:0: [sdb] Mode Sense: 43 00 10 08 [ 223.393660] iscsiadm[18136]: segfault at 7ffd9fa12e58 ip 555b0ccd95af sp 7ffd9fa12e60 error 6 in iscsiadm[555b0ccb4000+58000] [ 223.393666] Code: ba 00 02 00 00 48 81 ec 10 04 00 00 48 89 e7 48 8d 9c 24 00 02 00 00 64 48 8b 04 25 28 00 00 00 48 89 84 24 08 04 00 00 31 c0 3c ed 00 00 ba 00 02 00 00 4c 89 ee 48 89 e7 e8 6c ed 00 00 ba [ 223.394992] sd 1:0:0:0: alua: transition timeout set to 60 seconds [ 223.394997] sd 1:0:0:0: alua: port group 02 state N non-preferred supports TOlUSNA [ 223.395018] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 223.395435] Kernel panic - not syncing: Aiee, killing interrupt handler! [ 223.396802] sd 1:0:0:0: [sdb] Optimal transfer size 262144 bytes [ 223.402387] CPU: 6 PID: 18136 Comm: iscsiadm Kdump: loaded Tainted: G W 5.4.0-1033-gke #35~18.04.1-Ubuntu [ 223.402388] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [ 223.402389] Call Trace: [ 223.402395] dump_stack+0x6d/0x95 [ 223.402398] panic+0xfe/0x2e4 [ 223.402400] do_exit+0x899/0xb90 [ 223.402402] do_group_exit+0x43/0xa0 [ 223.402406] get_signal+0x14f/0x860 [ 223.402409] do_signal+0x34/0x6d0 [ 223.402414] ? __bad_area_nosemaphore+0x149/0x1f0 [ 223.457597] exit_to_usermode_loop+0x8e/0x100 [ 223.462090] prepare_exit_to_usermode+0x91/0xa0 [ 223.466782] retint_user+0x8/0x8 [ 223.470131] RIP: 0033:0x555b0ccd95af [ 223.473827] Code: ba 00 02 00 00 48 81 ec 10 04 00 00 48 89 e7 48 8d 9c 24 00 02 00 00 64 48 8b 04 25 28 00 00 00 48 89 84 24 08 04 00 00 31 c0 3c ed 00 00 ba 00 02 00 00 4c 89 ee 48 89 e7 e8 6c ed 00 00 ba [ 223.492991] RSP: 002b:7ffd9fa12e60 EFLAGS: 00010246 [
[Bug 1921825] Re: Kernel panic on `5.4.0-1033-gke` (Kernel panic - not syncing: Aiee, killing interrupt handler!) possibly iscsi related
** Also affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-gcp (Ubuntu) ** No longer affects: linux-gcp (Ubuntu Focal) ** Changed in: linux-gke (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gke (Ubuntu Focal) Assignee: (unassigned) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921825 Title: Kernel panic on `5.4.0-1033-gke` (Kernel panic - not syncing: Aiee, killing interrupt handler!) possibly iscsi related To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1921825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921825] Re: Kernel panic on `5.4.0-1033-gke` (Kernel panic - not syncing: Aiee, killing interrupt handler!) possibly iscsi related
60 RCX:
7f45793ce335
[ 223.505579] RDX: 0200 RSI: 555b0cf146a0 RDI:
7ffd9fa12e60
[ 223.513025] RBP: 7ffd9fa13ecc R08: R09:
80808000
[ 223.520268] R10: 0075 R11: 0246 R12:
7ffd9fa13540
[ 223.527521] R13: 7ffd9fa13540 R14: 0200 R15:
555b0d613300
+ Which happens during high iscsi activity
- Which happens during high iscsi activity
+
+ This issue is also identified in linux-5.8, reported here (
+ https://lkml.org/lkml/2020/7/28/1085 ) for example. It affects the
+ gcp-5.4 kernel specifically because gcp-5.4 has backported
+ '1b66d253610c7 ("bpf: Add get{peer, sock}name attach types for
+ sock_addr")' which introduces the issue.
+
+ The fix is
+
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bcf3a2953d36bbfb9bd44ccb3db0897d935cc485
+ from 5.9
** Changed in: linux-gcp (Ubuntu Focal)
Assignee: (unassigned) => Khaled El Mously (kmously)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921825
Title:
Kernel panic on `5.4.0-1033-gke` (Kernel panic - not syncing: Aiee,
killing interrupt handler!) possibly iscsi related
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1921825/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921825] [NEW] Kernel panic on `5.4.0-1033-gke` (Kernel panic - not syncing: Aiee, killing interrupt handler!) possibly iscsi related
Public bug reported: This stacktrace [ 223.386958] BUG: scheduling while atomic: iscsiadm/18136/0x0200 [ 223.393390] Modules linked in: tcp_diag inet_diag xt_nat ipt_REJECT nf_reject_ipv4 xt_tcpudp ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs sch_htb ebt_ip ebtable_filter ebtables veth xt_mark br_netfilter iptable_mangle xt_MASQUERADE xt_comment xt_addrtype iptable_nat binfmt_misc iptable_filter bpfilter xt_conntrack nf_nat bridge stp llc xfrm_user xfrm_algo aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper input_leds serio_raw sch_fq_codel sunrpc ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi virtio_rng ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear psmouse virtio_net net_failover failover [ 223.393429] CPU: 6 PID: 18136 Comm: iscsiadm Kdump: loaded Not tainted 5.4.0-1033-gke #35~18.04.1-Ubuntu [ 223.393430] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [ 223.393430] Call Trace: [ 223.393439] dump_stack+0x6d/0x95 [ 223.393464] __schedule_bug+0x55/0x70 [ 223.393467] __schedule+0x61b/0x710 [ 223.393469] schedule+0x33/0xa0 [ 223.393472] __lock_sock+0x7d/0xc0 [ 223.393475] ? wait_woken+0x80/0x80 [ 223.393477] lock_sock_nested+0x64/0x70 [ 223.393479] inet_getname+0xaa/0xe0 [ 223.393482] kernel_getpeername+0x1b/0x20 [ 223.393485] iscsi_sw_tcp_conn_get_param+0xa6/0x110 [iscsi_tcp] [ 223.393494] show_conn_ep_param_ISCSI_PARAM_CONN_ADDRESS+0x7e/0xa0 [scsi_transport_iscsi] [ 223.393496] dev_attr_show+0x1d/0x50 [ 223.393499] sysfs_kf_seq_show+0xa1/0x110 [ 223.393502] kernfs_seq_show+0x27/0x30 [ 223.393504] seq_read+0xda/0x420 [ 223.393506] kernfs_fop_read+0x141/0x1a0 [ 223.393510] __vfs_read+0x1b/0x40 [ 223.393512] vfs_read+0x8e/0x130 [ 223.393513] ksys_read+0xa7/0xe0 [ 223.393515] __x64_sys_read+0x1a/0x20 [ 223.393518] do_syscall_64+0x57/0x190 [ 223.393521] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 223.393523] RIP: 0033:0x7f45793ce910 [ 223.393525] Code: b6 fe ff ff 48 8d 3d 0f be 08 00 48 83 ec 08 e8 06 db 01 00 66 0f 1f 44 00 00 83 3d f9 2d 2c 00 00 75 10 b8 00 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 31 c3 48 83 ec 08 e8 de 9b 01 00 48 89 04 24 [ 223.393526] RSP: 002b:7ffd9fa13688 EFLAGS: 0246 ORIG_RAX: [ 223.393527] RAX: ffda RBX: 7ffd9fa13820 RCX: 7f45793ce910 [ 223.393528] RDX: 0100 RSI: 7ffd9fa13720 RDI: 0003 [ 223.393528] RBP: 7ffd9fa13720 R08: R09: [ 223.393529] R10: 0064 R11: 0246 R12: 0003 [ 223.393530] R13: 7ffd9fa13c60 R14: 555b0d613708 R15: 555b0d613300 [ 223.393581] sd 1:0:0:0: [sdb] Write Protect is off [ 223.393583] sd 1:0:0:0: [sdb] Mode Sense: 43 00 10 08 [ 223.393660] iscsiadm[18136]: segfault at 7ffd9fa12e58 ip 555b0ccd95af sp 7ffd9fa12e60 error 6 in iscsiadm[555b0ccb4000+58000] [ 223.393666] Code: ba 00 02 00 00 48 81 ec 10 04 00 00 48 89 e7 48 8d 9c 24 00 02 00 00 64 48 8b 04 25 28 00 00 00 48 89 84 24 08 04 00 00 31 c0 3c ed 00 00 ba 00 02 00 00 4c 89 ee 48 89 e7 e8 6c ed 00 00 ba [ 223.394992] sd 1:0:0:0: alua: transition timeout set to 60 seconds [ 223.394997] sd 1:0:0:0: alua: port group 02 state N non-preferred supports TOlUSNA [ 223.395018] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 223.395435] Kernel panic - not syncing: Aiee, killing interrupt handler! [ 223.396802] sd 1:0:0:0: [sdb] Optimal transfer size 262144 bytes [ 223.402387] CPU: 6 PID: 18136 Comm: iscsiadm Kdump: loaded Tainted: G W 5.4.0-1033-gke #35~18.04.1-Ubuntu [ 223.402388] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [ 223.402389] Call Trace: [ 223.402395] dump_stack+0x6d/0x95 [ 223.402398] panic+0xfe/0x2e4 [ 223.402400] do_exit+0x899/0xb90 [ 223.402402] do_group_exit+0x43/0xa0 [ 223.402406] get_signal+0x14f/0x860 [ 223.402409] do_signal+0x34/0x6d0 [ 223.402414] ? __bad_area_nosemaphore+0x149/0x1f0 [ 223.457597] exit_to_usermode_loop+0x8e/0x100 [ 223.462090] prepare_exit_to_usermode+0x91/0xa0 [ 223.466782] retint_user+0x8/0x8 [ 223.470131] RIP: 0033:0x555b0ccd95af [ 223.473827] Code: ba 00 02 00 00 48 81 ec 10 04 00 00 48 89 e7 48 8d 9c 24 00 02 00 00 64 48 8b 04 25 28 00 00 00 48 89 84 24 08 04 00 00 31 c0 3c ed 00 00 ba 00 02 00 00 4c 89 ee 48 89 e7 e8 6c ed 00 00 ba [ 223.492991] RSP: 002b:7ffd9fa12e60 EFLAGS: 00010246 [ 223.498333] RAX: RBX: 7ffd9fa13060 RCX: 7f45793ce335 [ 223.505579] RDX: 0200 RSI: 555b0cf146a0 RDI: 7ffd9fa12e60 [ 223.513025] RBP: 7ffd9fa13ecc R08:
[Bug 1908264] Re: Disable Atari partition support for cloud kernels
** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908264 Title: Disable Atari partition support for cloud kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1908264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914668] Re: Exploitable vulnerabilities in AF_VSOCK implementation
** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Also affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-riscv (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914668 Title: Exploitable vulnerabilities in AF_VSOCK implementation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910561] Re: Fix right sounds and mute/micmute LEDs for HP ZBook Fury 15/17 G7 Mobile Workstation
** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910561 Title: Fix right sounds and mute/micmute LEDs for HP ZBook Fury 15/17 G7 Mobile Workstation To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1910561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901842] Re: Ubuntu 20.04 - multicast counter is not increased in ip -s
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901842 Title: Ubuntu 20.04 - multicast counter is not increased in ip -s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908637] Re: psock_snd from net in ubuntu_kernel_selftests failed on G 5.8.0-34.37
*** This bug is a duplicate of bug 1892213 *** https://bugs.launchpad.net/bugs/1892213 ** This bug has been marked a duplicate of bug 1892213 psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908637 Title: psock_snd from net in ubuntu_kernel_selftests failed on G 5.8.0-34.37 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908637] [NEW] psock_snd from net in ubuntu_kernel_selftests failed on G 5.8.0-34.37
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/l/linux/20201218_030102_175b9@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/arm64/l/linux/20201217_165622_90478@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/ppc64el/l/linux/20201217_103407_ff212@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/s390x/l/linux/20201217_095421_b8712@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Summary changed: - linux 5.8.0-34.37 ADT test failure with linux 5.8.0-34.37 + psock_snd from net in ubuntu_kernel_selftests failed on G 5.8.0-34.37 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908637 Title: psock_snd from net in ubuntu_kernel_selftests failed on G 5.8.0-34.37 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908636] [NEW] udpgso_bench from net in ubuntu_kernel_selftests failed on G 5.8.0-34.37
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/l/linux/20201218_030102_175b9@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/arm64/l/linux/20201217_165622_90478@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/ppc64el/l/linux/20201217_103407_ff212@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/s390x/l/linux/20201217_095421_b8712@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Summary changed: - linux 5.8.0-34.37 ADT test failure with linux 5.8.0-34.37 + udpgso_bench from net in ubuntu_kernel_selftests failed on G/H 5.8.0-34.37 ** Summary changed: - udpgso_bench from net in ubuntu_kernel_selftests failed on G/H 5.8.0-34.37 + udpgso_bench from net in ubuntu_kernel_selftests failed on G 5.8.0-34.37 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908636 Title: udpgso_bench from net in ubuntu_kernel_selftests failed on G 5.8.0-34.37 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896077] Re: lttng-modules-dkms ADT test failure: build error with kernel >= 5.8
I responded to comment #4 at: https://bugs.launchpad.net/ubuntu/+source/lttng- modules/+bug/1903952/comments/4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896077 Title: lttng-modules-dkms ADT test failure: build error with kernel >= 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1896077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903952] Re: focal:linux-hwe-5.8 lttng-modules dkms failure
The upstream lttng-modules project is compatible and buildable on all >3.0 kernels. The new lttng-modules 2.12.2 code should continue to function fine on the 5.4 kernel. I confirmed that the this latest package builds and loads without any errors or warnings on the 5.4 kernel. Therefore, it is more accurate to say there is a small potential for regression on the 5.4 kernel - and that would likely indicate an upstream bug in lttng-modules itself. ** Description changed: Impact: lttng-modules-dkms fail to build on Focal with the linux-hwe-5.8 kernel. Fix: Use version 2.12.2 instead of 2.11.2. That would bring it in line with the version used in groovy. Testcase: Attempt to build the currently-available 2.11.2 - observe that it fails. Create a new package using the groovy source package, confirm that it builds and installs successfully. Furthermore, I was able to successfully manually modprobe all the .ko files that were built. - Regression potential: Technically this doesn't work on the 5.8 hwe - kernel in focal right now, so it cannot be any more broken than it - currently is. The 2.12.2 version is identical to the one currently used - in groovy. + Regression potential: Technically this doesn't work on the 5.8 hwe kernel in focal right now, so it cannot be any more broken than it currently is. The 2.12.2 version is identical to the one currently used in groovy. + EDIT: The upstream lttng-modules project is compatible and buildable on all >3.0 kernels. The new 2.12.2 code should continue to function fine on the 5.4 kernel. + + I confirmed that the this latest package builds and loads without any + errors or warnings on the 5.4 kernel. + + So, there is a small potential for regression on the 5.4 kernel - that + would likely indicate an upstream bug in lttng-modules itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903952 Title: focal:linux-hwe-5.8 lttng-modules dkms failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1903952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904654] Re: focal:linux-hwe-5.8 evdi-dkms build failure
..however, since the upstream project still supports 5.4 I expect potential for regression to be on the low side -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904654 Title: focal:linux-hwe-5.8 evdi-dkms build failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1904654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904654] Re: focal:linux-hwe-5.8 evdi-dkms build failure
@Robie, For this updated source, package, I have compiled it for the 5.4 kernel on Focal, and confirmed that: a) The module now builds properly on 5.4 b) The module is loadable into the 5.4 kernel (without errors or warnings) The upstream evdi project itself is compatible up to kernel 5.9: https://github.com/DisplayLink/evdi/commit/83046d3e6e55de2069bada70894c633c090f7ddc So I suppose there is a potential for regression on the 5.4 kernel, and that would likely indicate an upstream bug in evdi. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904654 Title: focal:linux-hwe-5.8 evdi-dkms build failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1904654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907262] Re: raid10: discard leads to corrupted file system
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907262 Title: raid10: discard leads to corrupted file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907262] Re: raid10: discard leads to corrupted file system
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907262 Title: raid10: discard leads to corrupted file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899832] Re: CONFIG options for (ipip, sit) should not be built-in to the KVM kernels
** Changed in: linux-kvm (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux-kvm (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux-kvm (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-kvm (Ubuntu Groovy) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899832 Title: CONFIG options for (ipip, sit) should not be built-in to the KVM kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1899832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899832] Re: CONFIG options for (ipip, sit) should not be built-in to the KVM kernels
** Description changed: CONFIG_NET_IPIP and CONFIG_IPV6_SIT are set to =y in the -kvm kernels. This means that they are always present in the kernel, and the virtual devices they created (tunl0 and sit0) are always present, even when not configured and not needed. This is causing some issues for clouds that use the -kvm flavour, and there is no good reason for those configuration options to be =y anyway. So they should be converted to =m instead. - [Regression potential] - - - I'm not aware of any. General consensus is that these options should - have been =m all along. + - The only possible regression I can think of by compiling these as modules is the possibility that someone's boot setup somehow depended on IP tunneling. Such issues would need to be worked out by some initramfs means, etc. + - After this change, the modules (ipip.ko, sit.ko) are present in linux-modules. + - General consensus was that these options should have been =m all along. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899832 Title: CONFIG options for (ipip, sit) should not be built-in to the KVM kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1899832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899832] Re: CONFIG options for (ipip, sit) should not be built-in to the KVM kernels
** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899832 Title: CONFIG options for (ipip, sit) should not be built-in to the KVM kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1899832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904654] Re: focal:linux-hwe-5.8 evdi-dkms build failure
Debdiff between 1.7.0+dfsg-1ubuntu1 and 1.7.0+dfsg-1ubuntu1~20.04.1 ** Attachment added: "Debdiff between 1.7.0+dfsg-1ubuntu1 and 1.7.0+dfsg-1ubuntu1~20.04.1" https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1904654/+attachment/5435369/+files/debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904654 Title: focal:linux-hwe-5.8 evdi-dkms build failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1904654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904654] Re: focal:linux-hwe-5.8 evdi-dkms build failure
debdiff between 1.6.0+dfsg-1 and 1.7.0+dfsg-1ubuntu1~20.04.1 ** Attachment added: "debdiff between 1.6.0+dfsg-1 and 1.7.0+dfsg-1ubuntu1~20.04.1" https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1904654/+attachment/5435374/+files/debdiff2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904654 Title: focal:linux-hwe-5.8 evdi-dkms build failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1904654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
