=== Guest4747 is now known as ogra [16:39] running xen in noble 24.04 with kernel-6.5, I see UBSAN kernel errors in xen-blkback and xen-netback drivers when domU launch [16:39] but everything works [16:40] in dmesg: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/block/xen-blkback/blkback.c:1227:4 [16:44] ChmEarl: since noble development is still early and i dont see xen related bugs on your case, might be worth a new bug? [16:44] unless some of our server testers can try to reproduce that first [16:45] lotuspsychje, ty, I was trying to see if there are any reproduce cases yet [16:45] my CPU is ancient, CORE2quad [16:47] ChmEarl: there are some other bugs with your ubsan error around though [16:47] bug #2002842 would be one [16:47] -ubottu:#ubuntu-next- Bug 2008157 in linux (Ubuntu) "[SRU][Ubuntu 22.04.1]: Observed 'Array Index out of bounds' Call Trace multiple times on Ubuntu 22.04.1 OS during boot" [Medium, In Progress] [duplicate: 2002842] https://launchpad.net/bugs/2008157 [16:47] I might try to run it on ivy-bridge soon [16:47] so, not sure its noble specific? [16:54] ChmEarl: an idea arising could be booting a previous kernel, to see if this is kernel related [16:56] lotuspsychje, not sure if I can run a kernel from mantic? or jammy? [16:56] there is only 1 kernel for noble [16:57] I was worried that its related to CPU support for stuff like: avx or aes [16:58] well its only for a test, if we assume your UBSAN error would only arise from kernel 6.5 for example [16:58] yes, thinking its specific to very recent kernel [16:59] im also thinking so [17:00] im seeing those UBSAN kernel errors in different bugs all over, not only xen [17:19] trying with 4 files from lunar: 6.2.0.20.20 [17:20] noble made no complaint [17:23] ok tnx for the test ChmEarl [17:29] so now to findout its really a useful warning to xen; or just an UBSAN default warning since a kernel version [17:44] lotuspsychje, the install of the lunar 6.2.0-20 packages worked, but xen/kernel-6.2 won't boot [17:44] at least I didn't waste hardly any time trying [17:45] what you can do is messing with later mainline kernels too [17:46] i didnt test xen myself so cant help there [17:49] the XEN & UBSAN configs are the same for the 2 kernels === tomreyn_ is now known as tomreyn [22:15] requesting a kernel-6.5 build with # CONFIG_UBSAN is not set [22:15] or turn-off array bound checks [22:16] xen domU is flooded with ubsan errors === JanC is now known as Guest2259 === JanC_ is now known as JanC