My zram module is configured to compress with LZ4. Obviously during zram's initialization (swap is not yet used by the system, as there is still plenty of free RAM), I got the following message in the kernel log: kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in ./include/linux/unaligned/access_ok.h:40:17 kernel: store to misaligned address 00000000dc8b829a for type '__le16' kernel: which requires 2 byte alignment kernel: CPU: 6 PID: 7414 Comm: mkswap Tainted: P O T 4.19.8-gentoo #1 kernel: Hardware name: ASUSTeK COMPUTER INC. G752VY/G752VY, BIOS G752VY.304 06/29/2017 kernel: Call Trace: kernel: dump_stack+0xa1/0x11b kernel: ubsan_epilogue+0x9/0x40 kernel: ubsan_type_mismatch_common+0x17b/0x190 kernel: __ubsan_handle_type_mismatch+0x43/0x60 kernel: LZ4_compress_default+0x29b6/0x3b20 [lz4_compress] kernel: lz4_compress_crypto+0x36/0xb0 [lz4] kernel: zram_bvec_rw.isra.11+0x438/0x1770 [zram] kernel: zram_make_request+0x25b/0x7c9 [zram] kernel: generic_make_request+0x301/0xa30 kernel: ? submit_bio+0x3d/0x390 kernel: submit_bio+0x3d/0x390 kernel: ? guard_bio_eod+0x69/0x450 kernel: submit_bh_wbc+0x2a6/0x600 kernel: __block_write_full_page+0x2b3/0xb80 kernel: ? block_llseek+0xa0/0xa0 kernel: ? clear_page_dirty_for_io+0x402/0x850 kernel: __writepage+0x31/0x90 kernel: write_cache_pages+0x2c5/0xa80 kernel: ? __wb_calc_thresh+0x310/0x310 kernel: generic_writepages+0x77/0xe0 kernel: ? blkdev_writepage+0x10/0x10 kernel: ? do_writepages+0x7e/0x120 kernel: do_writepages+0x7e/0x120 kernel: __filemap_fdatawrite_range+0x10e/0x1e0 kernel: file_write_and_wait_range+0x48/0xb0 kernel: blkdev_fsync+0x2e/0x90 kernel: do_fsync+0x33/0x60 kernel: __x64_sys_fsync+0x14/0x30 kernel: do_syscall_64+0x85/0x280 kernel: entry_SYSCALL_64_after_hwframe+0x49/0xbe kernel: RIP: 0033:0x7f2b12b39108 kernel: Code: 00 00 48 83 ec 28 64 48 8b 04 25 28 00 00 00 48 89 44 24 18 31 c0 48 8d 05 1d c7 2c 00 8b 00 85 c0 75 27 b8 4a 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 50 48 8b 74 24 18 64 48 33 34 25 28 00 00 00 kernel: RSP: 002b:00007ffc5a0dcdd0 EFLAGS: 00000246 ORIG_RAX: 000000000000004a kernel: RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f2b12b39108 kernel: RDX: 00007f2b12e00b00 RSI: 0000000000000000 RDI: 0000000000000003 kernel: RBP: 0000000000000000 R08: 0000000000000024 R09: 00007ffc5a0dcf00 kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffc5a0dcf00 kernel: R13: 000055580a786137 R14: 00000000000061b0 R15: 0000000000000000 kernel: ================================================================================ Some info: Portage 2.3.51 (python 3.6.5-final-0, hardened/linux/amd64, gcc-7.3.0, glibc-2.27-r6, 4.19.8-gentoo x86_64) ================================================================= System uname: Linux-4.19.8-gentoo-x86_64-Intel-R-_Core-TM-_i7-6700HQ_CPU_@_2.60GHz-with-gentoo-2.6 KiB Mem: 40976340 total, 16220132 free KiB Swap: 0 total, 0 free Timestamp of repository gentoo: Thu, 13 Dec 2018 12:15:01 +0000 Head commit of repository gentoo: 057645ffcdb86bd24e7c965f6e1aa03db33abb4c sh bash 4.4_p12 ld GNU ld (Gentoo 2.30 p5) 2.30.0 app-shells/bash: 4.4_p12::gentoo dev-java/java-config: 2.2.0-r4::gentoo dev-lang/perl: 5.26.2::gentoo dev-lang/python: 2.7.15::gentoo, 3.4.8::gentoo, 3.5.5::gentoo, 3.6.5::gentoo dev-util/cmake: 3.12.3::gentoo dev-util/pkgconfig: 0.29.2::gentoo sys-apps/baselayout: 2.6-r1::gentoo sys-apps/openrc: 0.38.3-r1::gentoo sys-apps/sandbox: 2.13::gentoo sys-devel/autoconf: 2.13::gentoo, 2.69-r4::gentoo sys-devel/automake: 1.11.6-r3::gentoo, 1.12.6::gentoo, 1.13.4-r2::gentoo, 1.14.1::gentoo, 1.15.1-r2::gentoo sys-devel/binutils: 2.30-r4::gentoo sys-devel/gcc: 7.3.0-r3::gentoo sys-devel/gcc-config: 1.8-r1::gentoo sys-devel/libtool: 2.4.6-r3::gentoo sys-devel/make: 4.2.1-r4::gentoo sys-kernel/linux-headers: 4.13::gentoo (virtual/os-headers) sys-libs/glibc: 2.27-r6::gentoo
Another UBSAN message for the same header, this time line 45: kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in ./include/linux/unaligned/access_ok.h:45:17 kernel: store to misaligned address 00000000807e9d9b for type '__le32' kernel: which requires 4 byte alignment kernel: CPU: 6 PID: 7414 Comm: mkswap Tainted: P O T 4.19.8-gentoo #1 kernel: Hardware name: ASUSTeK COMPUTER INC. G752VY/G752VY, BIOS G752VY.304 06/29/2017 kernel: Call Trace: kernel: dump_stack+0xa1/0x11b kernel: ubsan_epilogue+0x9/0x40 kernel: ubsan_type_mismatch_common+0x17b/0x190 kernel: __ubsan_handle_type_mismatch+0x43/0x60 kernel: LZ4_compress_default+0x2fe9/0x3b20 [lz4_compress] kernel: lz4_compress_crypto+0x36/0xb0 [lz4] kernel: zram_bvec_rw.isra.11+0x438/0x1770 [zram] kernel: zram_make_request+0x25b/0x7c9 [zram] kernel: generic_make_request+0x301/0xa30 kernel: ? submit_bio+0x3d/0x390 kernel: submit_bio+0x3d/0x390 kernel: ? guard_bio_eod+0x69/0x450 kernel: submit_bh_wbc+0x2a6/0x600 kernel: __block_write_full_page+0x2b3/0xb80 kernel: ? block_llseek+0xa0/0xa0 kernel: ? clear_page_dirty_for_io+0x402/0x850 kernel: __writepage+0x31/0x90 kernel: write_cache_pages+0x2c5/0xa80 kernel: ? __wb_calc_thresh+0x310/0x310 kernel: generic_writepages+0x77/0xe0 kernel: ? blkdev_writepage+0x10/0x10 kernel: ? do_writepages+0x7e/0x120 kernel: do_writepages+0x7e/0x120 kernel: __filemap_fdatawrite_range+0x10e/0x1e0 kernel: file_write_and_wait_range+0x48/0xb0 kernel: blkdev_fsync+0x2e/0x90 kernel: do_fsync+0x33/0x60 kernel: __x64_sys_fsync+0x14/0x30 kernel: do_syscall_64+0x85/0x280 kernel: entry_SYSCALL_64_after_hwframe+0x49/0xbe kernel: RIP: 0033:0x7f2b12b39108 kernel: Code: 00 00 48 83 ec 28 64 48 8b 04 25 28 00 00 00 48 89 44 24 18 31 c0 48 8d 05 1d c7 2c 00 8b 00 85 c0 75 27 b8 4a 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 50 48 8b 74 24 18 64 48 33 34 25 28 00 00 00 kernel: RSP: 002b:00007ffc5a0dcdd0 EFLAGS: 00000246 ORIG_RAX: 000000000000004a kernel: RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f2b12b39108 kernel: RDX: 00007f2b12e00b00 RSI: 0000000000000000 RDI: 0000000000000003 kernel: RBP: 0000000000000000 R08: 0000000000000024 R09: 00007ffc5a0dcf00 kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffc5a0dcf00 kernel: R13: 000055580a786137 R14: 00000000000061b0 R15: 0000000000000000 kernel: ================================================================================ Same system as above.
...and for line 50: kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in ./include/linux/unaligned/access_ok.h:50:17 kernel: store to misaligned address 00000000129e205e for type '__le64' kernel: which requires 8 byte alignment kernel: CPU: 0 PID: 7415 Comm: swapon Tainted: P O T 4.19.8-gentoo #1 kernel: Hardware name: ASUSTeK COMPUTER INC. G752VY/G752VY, BIOS G752VY.304 06/29/2017 kernel: Call Trace: kernel: dump_stack+0xa1/0x11b kernel: ubsan_epilogue+0x9/0x40 kernel: ubsan_type_mismatch_common+0x17b/0x190 kernel: __ubsan_handle_type_mismatch+0x43/0x60 kernel: LZ4_decompress_safe+0x853/0x960 kernel: lz4_decompress_crypto+0x24/0x80 [lz4] kernel: zcomp_decompress+0x4b/0xb0 [zram] kernel: zram_bvec_rw.isra.11+0x86e/0x1770 [zram] kernel: zram_rw_page+0xdf/0x1a0 [zram] kernel: ? zram_bvec_rw.isra.11+0x1770/0x1770 [zram] kernel: bdev_read_page+0xdd/0x1f0 kernel: do_mpage_readpage+0x844/0x14b0 kernel: ? add_to_page_cache_lru+0xc7/0x1b0 kernel: mpage_readpages+0x196/0x380 kernel: ? block_llseek+0xa0/0xa0 kernel: ? get_page_from_freelist+0x1899/0x3690 kernel: read_pages+0xa2/0x3c0 kernel: ? __do_page_cache_readahead+0x213/0x360 kernel: __do_page_cache_readahead+0x213/0x360 kernel: ondemand_readahead+0x316/0xd90 kernel: generic_file_read_iter+0xac8/0x1920 kernel: new_sync_read+0x1d7/0x4f0 kernel: vfs_read+0xa2/0x290 kernel: ksys_read+0x5c/0x100 kernel: do_syscall_64+0x85/0x280 kernel: entry_SYSCALL_64_after_hwframe+0x49/0xbe kernel: RIP: 0033:0x7f86841cbd45 kernel: Code: 00 00 0f 1f 00 48 83 ec 38 64 48 8b 04 25 28 00 00 00 48 89 44 24 28 31 c0 48 8d 05 dd 3a 2d 00 8b 00 85 c0 75 27 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 63 48 8b 4c 24 28 64 48 33 0c 25 28 00 00 00 kernel: RSP: 002b:00007ffd93dc2250 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f86841cbd45 kernel: RDX: 0000000000010000 RSI: 0000557bbb60d5d0 RDI: 0000000000000003 kernel: RBP: 0000557bbb60c5c0 R08: 0000000000000003 R09: 00007f868449ae30 kernel: R10: 0000000000000001 R11: 0000000000000246 R12: 0000000000000003 kernel: R13: 00007ffd93dc2490 R14: 00007ffd93dc24cc R15: 0000557bbb60d5d0 kernel: ================================================================================
Are you sure 17 related bug reports are needed?
You mean the various UBSAN "undefined behaviour" bug reports I posted on January 10, 2019? They all concern different programs, different headers etc. The program/header is named on the report title. Inside each one of my UBSAN reports I gather "undefined behaviour" messages for different lines of the same program or header. It is not at all clear to me that all those bug reports are "related" in any way - can you please provide some proof of this and how I am supposed to check this before reporting?
(In reply to segmentation fault from comment #4) > You mean the various UBSAN "undefined behaviour" bug reports I posted on > January 10, 2019? They all concern different programs, different headers > etc. The program/header is named on the report title. Inside each one of my > UBSAN reports I gather "undefined behaviour" messages for different lines of > the same program or header. > > It is not at all clear to me that all those bug reports are "related" in any > way - can you please provide some proof of this and how I am supposed to > check this before reporting? Seriously. I'm with Tomáš on this one. Anyways, test with the latest 4.19.X which is 4.19.14 right now. If it fails, then test with the latest 4.20.X which is 4.20.1. If they all fail, then do a bisect with the last working kernel and 4.19.8.
I'm not sure what kind of bugfix you're expecting an unaligned access warning in a file called unaligned/access_ok.h to result in?
(In reply to segmentation fault from comment #4) > You mean the various UBSAN "undefined behaviour" bug reports I posted on > January 10, 2019? They all concern different programs, different headers > etc. The program/header is named on the report title. Inside each one of my > UBSAN reports I gather "undefined behaviour" messages for different lines of > the same program or header. > > It is not at all clear to me that all those bug reports are "related" in any > way - can you please provide some proof of this and how I am supposed to > check this before reporting? Yes, i meant all those bug reports with very similar subject "kernel 4.19.8: Undefined behaviour in ...". I think they could be posted in one bug report, first adding a summary and then adding attachments for example. If someone is interested in the topic, he will just CC himself once and not 18 times. And the bug wranglers only assign the bug once :)
O.K., got it, for the next time. I thought of it as follows: there are different programs involved, maintained by different persons upstream. So it would be easier (and nicer) to point a report about undefined behaviour in program X to the developer of program X - instead of pointing the developer of X to a huge report regarding X, Y, Z...
Anthony, I was baffled by the name (unaligned/access_ok.h) and I opened it in an editor. However, I was not able to make sure (by looking at its code) that "unaligned/access_ok.h" was named this way because the naming semantics was "this is a header that deals with unaligned access, which is O.K. to be unaligned" or rather "this is a header that deals with unaligned access, which is NOT O.K. and we are trying to make the access O.K. with the macros defined here" I did not have the time (and the willingness) to delve into the programming details, so I preferred to err on the side of caution and reported it. If the first interpretation of its name is the right one, then maybe someone should put a big, fat warning on top of that header: DO NOT REPORT UBSAN MESSAGES REGARDING THIS HEADER! UNALIGNED ACCESS IS A FEATURE, NOT A BUG OF THIS FILE! :-)
(In reply to segmentation fault from comment #8) > I thought of it as follows: there are different programs involved, > maintained by different persons upstream. So it would be easier (and nicer) > to point a report about undefined behaviour in program X to the developer of > program X - instead of pointing the developer of X to a huge report > regarding X, Y, Z... All of those bug reports were asigned to kernel team and i don't see any programs mentioned in the bug reports either: kernel 4.19.8: Undefined behaviour in net/ipv4/af_inet.c:1409:13 kernel 4.19.8: Undefined behaviour in ./include/net/ip.h:347:13 kernel 4.19.8: Undefined behaviour in net/ipv4/udp.c:537:9 kernel 4.19.8: Undefined behaviour in net/ipv4/ip_input.c:458:9 kernel 4.19.8: Undefined behaviour in net/netfilter/nf_conntrack_core.c:304:9 kernel 4.19.8: Undefined behaviour in net/ipv4/netfilter/ip_tables.c:256:18 kernel 4.19.8: Undefined behaviour in net/ipv4/netfilter/nf_log_ipv4.c:65:46 kernel 4.19.8: kernel: Undefined behaviour in ./include/uapi/linux/swab.h:179:9 kernel 4.19.8: Undefined behaviour in net/netfilter/nf_conntrack_proto_tcp.c:876:28 kernel 4.19.8: Undefined behaviour in ./include/linux/etherdevice.h:139:17 kernel 4.19.8: Undefined behaviour in net/netfilter/xt_tcpudp.c:96:4 kernel 4.19.8: Undefined behaviour in net/unix/garbage.c:301:2 They all seem to me like kernel "bugs", doesn't matter which userspace programs actually triggered them. In case there are multiple applications involved i agree it's better to open separate bug reports, but it doesn't seem to me it's this case.
Now, let me give you some feedback: As you can see from my 'system info', I had linux-headers-4.13 installed, while I switched to kernel 4.19.8 from gentoo-sources. Seeing all those UBSAN messages, especially the ones regarding networking, I thought that maybe some programs were linked with the wrong headers, so I upgraded to linux-headers-4.19 and re-merged all packages that explicitly depended on linux-headers. These were: app-emulation/qemu app-misc/srm dev-libs/libbsd dev-qt/qtgui dev-util/perf dev-util/strace media-gfx/sane-backends media-video/ffmpeg media-video/transcode net-dialup/rp-pppoe net-firewall/iptables net-misc/lksctp-tools net-misc/networkmanager sys-apps/busybox sys-apps/hwinfo sys-apps/iproute2 sys-apps/keyutils sys-fs/udev sys-fs/udisks sys-libs/efivar sys-libs/libcap sys-libs/libcap-ng sys-libs/libseccomp sys-libs/mtdev sys-power/acpid sys-process/audit virtual/linuxtv-dvb-headers virtual/os-headers x11-drivers/xf86-input-evdev x11-drivers/xf86-input-synaptics It is interesting that the networking-related packages sys-apps/iproute2 and net-firewall/iptables were among them. I could rebuild all of them, with the exception of sys-process/audit, which seems unrelated to the issue here. After restarting the firewall and working a bit with this system, I notice that my kernel log has become extremely quiet - especially there are no new UBSAN messages regarding the network stack! So maybe it was a false alarm, after all. Or maybe the 4.13 headers should NOT produce such messages, in which case the alarm remains valid...? I am not an expert in header compatibility inside major kernel versions, so maybe those reports uncovered something that should not happen, or maybe it was my fault. If I learned something with Gentoo all those years, is this: there IS a reason behind this outcome. NOTHING is without a cause. It's all about whether one is willing the pay the price to find it, or not. A nice day to all of you - and THANK YOU for the hard work you put into this!
Just to clarify: when I said 'programs', I meant the programs mentioned on the report titles, namely: net/ipv4/af_inet.c include/net/ip.h net/ipv4/udp.c net/ipv4/ip_input.c net/netfilter/nf_conntrack_core.c net/ipv4/netfilter/ip_tables.c net/ipv4/netfilter/nf_log_ipv4.c include/uapi/linux/swab.h net/netfilter/nf_conntrack_proto_tcp.c include/linux/etherdevice.h net/netfilter/xt_tcpudp.c net/unix/garbage.c I doubt, for example, that the developers of net/unix/garbage.c are the same ones that take also care of include/uapi/linux/swab.h, or net/netfilter/nf_conntrack_core.c, or... In that sense, I thought it was better to keep the reports separate, so that the netfilter developers can look at their part, without having to skim over the part of the uapi team - and so on.
I see, but this is not the kernel bugzilla :) It's a single package - gentoo-sources - which is as a whole maintained by the same people.
I was too quick to conclude that compiling those packages against linux-headers-4.19 (instead of 4.13) has eliminated the UBSAN messages for programs related to networking. Those messages are still there. And here is another one, this time for kernel/tsacct.c: kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in kernel/tsacct.c:52:19 kernel: member access within misaligned address 0000000009a615d4 for type 'struct taskstats' kernel: which requires 8 byte alignment kernel: CPU: 3 PID: 4366 Comm: iotop Tainted: P O T 4.19.8-gentoo #4 kernel: Hardware name: ASUSTeK COMPUTER INC. G752VY/G752VY, BIOS G752VY.304 06/29/2017 kernel: Call Trace: kernel: dump_stack+0xa1/0x11b kernel: ubsan_epilogue+0x9/0x40 kernel: ubsan_type_mismatch_common+0x17b/0x190 kernel: __ubsan_handle_type_mismatch+0x43/0x60 kernel: bacct_add_tsk+0x50d/0x740 kernel: fill_stats+0xa5/0x150 kernel: taskstats_user_cmd+0x516/0xa40 kernel: ? nla_parse+0x14f/0x2b0 kernel: genl_family_rcv_msg+0x38e/0xde0 kernel: genl_rcv_msg+0x60/0x120 kernel: ? genl_family_rcv_msg+0xde0/0xde0 kernel: netlink_rcv_skb+0x9b/0x2e0 kernel: ? __netlink_lookup+0x137/0x270 kernel: genl_rcv+0x1f/0x30 kernel: netlink_unicast+0x25d/0x440 kernel: netlink_sendmsg+0x3f1/0x8a0 kernel: __sys_sendto+0x179/0x230 kernel: __x64_sys_sendto+0x53/0x150 kernel: do_syscall_64+0x85/0x280 kernel: entry_SYSCALL_64_after_hwframe+0x49/0xbe kernel: RIP: 0033:0x7f9b29553cff kernel: Code: 83 ec 30 64 48 8b 04 25 28 00 00 00 48 89 44 24 28 31 c0 8b 05 72 c4 20 00 85 c0 75 36 45 31 c9 45 31 c0 b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 79 48 8b 5c 24 28 64 48 33 1c 25 28 00 00 00 kernel: RSP: 002b:00007ffe7da6e3b0 EFLAGS: 00000246 ORIG_RAX: 000000000000002c kernel: RAX: ffffffffffffffda RBX: 00007ffe7da6e4a0 RCX: 00007f9b29553cff kernel: RDX: 000000000000001c RSI: 00007f9b279f5510 RDI: 0000000000000005 kernel: RBP: 0000564a9664f800 R08: 0000000000000000 R09: 0000000000000000 kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 00007f9b2734b6a8 kernel: R13: 00007ffe7da6e4a0 R14: 00007f9b26ccc1b0 R15: 0000564a9664f800 kernel: ================================================================================ In fact, there is a whole lot of them, for various lines, but I will not post them all here. Smilar with kernel/delayacct.c: kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in kernel/delayacct.c:140:21 kernel: member access within misaligned address 0000000009a615d4 for type 'struct taskstats' kernel: which requires 8 byte alignment kernel: CPU: 3 PID: 4366 Comm: iotop Tainted: P O T 4.19.8-gentoo #4 kernel: Hardware name: ASUSTeK COMPUTER INC. G752VY/G752VY, BIOS G752VY.304 06/29/2017 kernel: Call Trace: kernel: dump_stack+0xa1/0x11b kernel: ubsan_epilogue+0x9/0x40 kernel: ubsan_type_mismatch_common+0x17b/0x190 kernel: __ubsan_handle_type_mismatch+0x43/0x60 kernel: __delayacct_add_tsk+0x3e0/0x820 kernel: fill_stats+0xd0/0x150 kernel: taskstats_user_cmd+0x516/0xa40 kernel: ? nla_parse+0x14f/0x2b0 kernel: genl_family_rcv_msg+0x38e/0xde0 kernel: ? lookup_fast+0x17d/0x590 kernel: genl_rcv_msg+0x60/0x120 kernel: ? genl_family_rcv_msg+0xde0/0xde0 kernel: netlink_rcv_skb+0x9b/0x2e0 kernel: ? __netlink_lookup+0x137/0x270 kernel: genl_rcv+0x1f/0x30 kernel: netlink_unicast+0x25d/0x440 kernel: netlink_sendmsg+0x3f1/0x8a0 kernel: __sys_sendto+0x179/0x230 kernel: __x64_sys_sendto+0x53/0x150 kernel: do_syscall_64+0x85/0x280 kernel: entry_SYSCALL_64_after_hwframe+0x49/0xbe kernel: RIP: 0033:0x7f9b29553cff kernel: Code: 83 ec 30 64 48 8b 04 25 28 00 00 00 48 89 44 24 28 31 c0 8b 05 72 c4 20 00 85 c0 75 36 45 31 c9 45 31 c0 b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 79 48 8b 5c 24 28 64 48 33 1c 25 28 00 00 00 kernel: RSP: 002b:00007ffe7da6e3b0 EFLAGS: 00000246 ORIG_RAX: 000000000000002c kernel: RAX: ffffffffffffffda RBX: 00007ffe7da6e4a0 RCX: 00007f9b29553cff kernel: RDX: 000000000000001c RSI: 00007f9b279f0a90 RDI: 0000000000000005 kernel: RBP: 0000564a9664f800 R08: 0000000000000000 R09: 0000000000000000 kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 00007f9b2734b6a8 kernel: R13: 00007ffe7da6e4a0 R14: 00007f9b26ccc1b0 R15: 0000564a9664f800 kernel: ================================================================================ ...and another one, for net/ipv4/igmp.c: kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in net/ipv4/igmp.c:985:24 kernel: member access within misaligned address 000000007375b62d for type 'struct igmpv3_query' kernel: which requires 4 byte alignment kernel: CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O T 4.19.8-gentoo #4 kernel: Hardware name: ASUSTeK COMPUTER INC. G752VY/G752VY, BIOS G752VY.304 06/29/2017 kernel: Call Trace: kernel: <IRQ> kernel: dump_stack+0xa1/0x11b kernel: ubsan_epilogue+0x9/0x40 kernel: ubsan_type_mismatch_common+0x17b/0x190 kernel: __ubsan_handle_type_mismatch+0x43/0x60 kernel: igmp_rcv+0x1b4a/0x1d10 kernel: ? ubsan_epilogue+0x24/0x40 kernel: ip_local_deliver_finish+0x106/0x6a0 kernel: ip_local_deliver+0xc4/0x1c0 kernel: ? ip_sublist_rcv+0x7f0/0x7f0 kernel: ip_rcv+0x7b/0x100 kernel: ? nf_hook.constprop.9+0x2f0/0x2f0 kernel: ? ip_local_deliver+0x1c0/0x1c0 kernel: __netif_receive_skb_one_core+0x6b/0xd0 kernel: ? swiotlb_sync_single_for_cpu+0x10/0x10 kernel: netif_receive_skb_internal+0x42/0x180 kernel: napi_gro_receive+0x13e/0x1d0 kernel: ? swiotlb_sync_single_for_cpu+0x10/0x10 kernel: rtl8169_poll+0x3a2/0x1630 [r8169] kernel: net_rx_action+0x39b/0x11d0 kernel: __do_softirq+0x1ee/0x86e kernel: irq_exit+0xae/0x110 kernel: do_IRQ+0xa1/0x150 kernel: common_interrupt+0xf/0xf kernel: </IRQ> kernel: RIP: 0010:cpuidle_enter_state+0x116/0x650 kernel: Code: 48 c7 44 24 18 00 00 00 00 0f 1f 44 00 00 31 ff e8 9f 82 ba fe 45 84 ff 0f 85 5d 02 00 00 e8 61 2d d6 fe fb 66 0f 1f 44 00 00 <4c> 8b 2c 24 4d 29 f5 0f 80 fa 02 00 00 4c 89 e8 48 ba cf f7 53 e3 kernel: RSP: 0018:ffffa688400d7e48 EFLAGS: 00000286 ORIG_RAX: ffffffffffffffd9 kernel: RAX: 0000000000000000 RBX: ffffc6883fd08a00 RCX: 000000000000001f kernel: RDX: 0000000000000035 RSI: 000000003161f9ae RDI: 0000000000000000 kernel: RBP: ffffffff93b9b438 R08: 0000000000000000 R09: 0000000000000000 kernel: R10: ffffa688400d7e08 R11: ffffffffc0a5b8c0 R12: 0000000000000008 kernel: R13: 0000000000000004 R14: 0000001db87d864a R15: 0000000000000000 kernel: ? _nv033845rm+0x150/0x440 [nvidia] kernel: ? cpuidle_enter_state+0x10f/0x650 kernel: do_idle+0x1ec/0x2c0 kernel: cpu_startup_entry+0x77/0x90 kernel: start_secondary+0x206/0x2e0 kernel: secondary_startup_64+0xb6/0xc0 kernel: ================================================================================
Yet another, for net/ipv4/tcp_minisocks.c: kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in net/ipv4/tcp_minisocks.c:536:19 kernel: member access within misaligned address 0000000023960a32 for type 'struct tcphdr' kernel: which requires 4 byte alignment kernel: CPU: 7 PID: 3705 Comm: EMT Tainted: P O T 4.19.8-gentoo #4 kernel: Hardware name: ASUSTeK COMPUTER INC. G752VY/G752VY, BIOS G752VY.304 06/29/2017 kernel: Call Trace: kernel: <IRQ> kernel: dump_stack+0xa1/0x11b kernel: ubsan_epilogue+0x9/0x40 kernel: ubsan_type_mismatch_common+0x17b/0x190 kernel: __ubsan_handle_type_mismatch+0x43/0x60 kernel: tcp_create_openreq_child+0x101c/0x13c0 kernel: tcp_v4_syn_recv_sock+0x7f/0xc00 kernel: ? ubsan_type_mismatch_common+0x17b/0x190 kernel: tcp_check_req+0x503/0x10d0 kernel: tcp_v4_rcv+0xcf8/0x2170 kernel: ip_local_deliver_finish+0x106/0x6a0 kernel: ip_local_deliver+0xc4/0x1c0 kernel: ? ip_sublist_rcv+0x7f0/0x7f0 kernel: ip_rcv+0x7b/0x100 kernel: ? nf_hook.constprop.9+0x2f0/0x2f0 kernel: ? ip_local_deliver+0x1c0/0x1c0 kernel: __netif_receive_skb_one_core+0x6b/0xd0 kernel: process_backlog+0x10a/0x6b0 kernel: net_rx_action+0x39b/0x11d0 kernel: __do_softirq+0x1ee/0x86e kernel: do_softirq_own_stack+0x44/0x60 kernel: </IRQ> kernel: do_softirq.part.19+0x61/0x90 kernel: netif_rx_ni+0x49/0x100 kernel: vboxNetFltPortOsXmit+0x68/0xe0 [vboxnetflt] kernel: vboxNetFltTryRetainBusyActive+0x101/0x350 [vboxnetflt] kernel: ? SUPR0ObjAddRefEx+0x257/0x720 [vboxdrv] kernel: ? _raw_spin_unlock+0x5/0x10 kernel: ? VBoxHost_RTHandleTableLookupWithCtx+0x124/0x310 [vboxdrv] kernel: ? update_load_avg+0x12e/0x1900 kernel: ? select_task_rq_fair+0x4ac/0x3bc0 kernel: ? account_entity_enqueue+0x168/0x330 kernel: ? enqueue_task_fair+0x1e0/0x1bf0 kernel: ? try_to_wake_up+0x63/0xda0 kernel: ? pollwake+0xa4/0x160 kernel: ? supdrvIOCtlFast+0xef/0x270 [vboxdrv] kernel: ? SUPR0Printf+0x12a/0x390 [vboxdrv] kernel: ? SUPR0Printf+0xb0/0x390 [vboxdrv] kernel: ? do_vfs_ioctl+0xe5/0xe80 kernel: ? __fget_light+0x109/0x1c0 kernel: ? ksys_ioctl+0x35/0x60 kernel: ? __x64_sys_ioctl+0x2b/0x80 kernel: ? do_syscall_64+0x85/0x280 kernel: ? entry_SYSCALL_64_after_hwframe+0x49/0xbe kernel: ================================================================================
(In reply to Mike Pagano from comment #5) > > Anyways, test with the latest 4.19.X which is 4.19.14 right now. > If it fails, then test with the latest 4.20.X which is 4.20.1. > > If they all fail, then do a bisect with the last working kernel and 4.19.8. Please try this.
(In reply to Tomáš Mózes from comment #16) > (In reply to Mike Pagano from comment #5) > > > > Anyways, test with the latest 4.19.X which is 4.19.14 right now. > > If it fails, then test with the latest 4.20.X which is 4.20.1. > > > > If they all fail, then do a bisect with the last working kernel and 4.19.8. > > Please try this. O.K. I've spent a day compiling 4.19.15, including nvidia-drivers and virtualbox*, as well as app-arch/lbzip2 app-arch/bzip2 sci-libs/netcdf sci-libs/netcdf-cxx sys-process/procps app-arch/lz4 sys-apps/util-linux app-editors/vim The reason for rebuilding the packages that are not directly related to the kernel change was that all those UBSAN messages had to do with lbzip2, lz4, ps, vi... (sci-libs/netcdf is the owner of /usr/lib64/libbzip2.so here). Of course, they might be unrelated, since 'ps', 'vi' are programs I constantly use and UBSAN messages that mention, say, 'lz4', mean the kernel module lz4 and not any component of app-arch/lz4. But at this point I am quite desperate to get rid of UBSAN messages that really litter my kernel log. So, to make it short, yes, I tried 4.19.15 so far and the messages persist - as far as I can say, all of them, so I will not repost them here. Now, before I spend another day doing the above for kernel 4.20.2, which is the latest one currently, I would like to know from you who are reading this: do you have a *founded* reason to believe that those issues have been taken care of in the 4.20.x kernels, or is it just a 'hope'? Did the lines mentioned in the UBSAN messages change from 4.19.15 to 4.20.x? If not, just trying new kernels is an exercise in futility. What I will do in the meantime, is the following: I will rebuild app-arch/bzip2 with -abi_x86_32, so that is is only present in 64-bit. I had to add the abi_x86_32 use flag, because some packages seemed to require it, but maybe this is not necessary anymore and just confuses some configure script...
There is a new UBSAN message, in kernel 4.19.15, regarding ptrace, that was obviously the result of running ebuild.sh: kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in kernel/ptrace.c:564:2 kernel: member access within misaligned address 000000002f7cfa83 for type 'struct task_struct' kernel: which requires 64 byte alignment kernel: CPU: 7 PID: 30610 Comm: ebuild.sh Tainted: P O T 4.19.15-gentoo #2 kernel: Hardware name: ASUSTeK COMPUTER INC. G752VY/G752VY, BIOS G752VY.304 06/29/2017 kernel: Call Trace: kernel: dump_stack+0xa1/0x11b kernel: ubsan_epilogue+0x9/0x40 kernel: ubsan_type_mismatch_common+0x17b/0x190 kernel: __ubsan_handle_type_mismatch+0x43/0x60 kernel: exit_ptrace+0x1e7/0x230 kernel: ? css_set_move_task+0x155/0x680 kernel: forget_original_parent+0x62e/0xfc0 kernel: ? cgroup_exit+0x140/0x220 kernel: do_exit+0x512/0x13e0 kernel: do_group_exit+0x6a/0x220 kernel: __x64_sys_exit_group+0x18/0x30 kernel: do_syscall_64+0x85/0x280 kernel: entry_SYSCALL_64_after_hwframe+0x49/0xbe kernel: RIP: 0033:0x7f3c7f13df96 kernel: Code: Bad RIP value. kernel: RSP: 002b:00007ffdf9e819f8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 kernel: RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f3c7f13df96 kernel: RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000 kernel: RBP: 0000000000000011 R08: 00000000000000e7 R09: ffffffffffffff80 kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 00007f3c7fa51010 kernel: R13: 0000000000000001 R14: 00007ffdf9e82160 R15: 00007ffdf9e82180 kernel: ================================================================================ For those interested, I get these messages because I compile my kernels with: CONFIG_UBSAN=y CONFIG_UBSAN_SANITIZE_ALL=y CONFIG_UBSAN_ALIGNMENT=y to be found under 'Kernel hacking': [*] Undefined behaviour sanity checker [*] Enable instrumentation for the entire kernel [*] Enable checking of pointers alignment I would love to know if others get them too, with those settings in place.
...and yet another (quite scary, this one) for XFS b-tree allocation pointers: kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in fs/xfs/libxfs/xfs_ialloc_btree.c:52:22 kernel: member access within misaligned address 00000000c1ce4cdf for type 'union xfs_btree_ptr' kernel: which requires 8 byte alignment kernel: CPU: 1 PID: 17119 Comm: rm Tainted: P O T 4.19.15-gentoo #2 kernel: Hardware name: ASUSTeK COMPUTER INC. G752VY/G752VY, BIOS G752VY.304 06/29/2017 kernel: Call Trace: kernel: dump_stack+0xa1/0x11b kernel: ubsan_epilogue+0x9/0x40 kernel: ubsan_type_mismatch_common+0x17b/0x190 kernel: __ubsan_handle_type_mismatch+0x43/0x60 kernel: xfs_inobt_set_root+0x117/0x140 [xfs] kernel: xfs_btree_kill_root+0x167/0x460 [xfs] kernel: ? xfs_btree_ptr_offset+0x8e/0x1e0 [xfs] kernel: xfs_btree_delrec+0xf71/0x2590 [xfs] kernel: ? xfs_btree_lookup_get_block+0x168/0x4a0 [xfs] kernel: ? __radix_tree_lookup+0x70/0x100 kernel: xfs_btree_delete+0x40/0x250 [xfs] kernel: ? xfs_perag_get+0x35/0x140 [xfs] kernel: xfs_difree_inobt+0x429/0x780 [xfs] kernel: xfs_difree+0x130/0x4e0 [xfs] kernel: ? xfs_trans_reserve+0x2b2/0x6e0 [xfs] kernel: xfs_ifree+0x81/0x4a0 [xfs] kernel: xfs_inactive_ifree+0xc6/0x2b0 [xfs] kernel: xfs_inactive+0x104/0x320 [xfs] kernel: xfs_fs_destroy_inode+0x20b/0x700 [xfs] kernel: do_unlinkat+0x1f9/0x590 kernel: do_syscall_64+0x85/0x280 kernel: entry_SYSCALL_64_after_hwframe+0x49/0xbe kernel: RIP: 0033:0x7f0e82080ba7 kernel: Code: 73 01 c3 48 8b 0d e9 c2 2c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 07 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b9 c2 2c 00 f7 d8 64 89 01 48 kernel: RSP: 002b:00007fffe950acf8 EFLAGS: 00000246 ORIG_RAX: 0000000000000107 kernel: RAX: ffffffffffffffda RBX: 000055c4f73a2e40 RCX: 00007f0e82080ba7 kernel: RDX: 0000000000000000 RSI: 000055c4f73a2f48 RDI: 0000000000000007 kernel: RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000 kernel: R10: fffffffffffff000 R11: 0000000000000246 R12: 000055c4f735d480 kernel: R13: 00007fffe950ae30 R14: 000055c4f73a2e40 R15: 0000000000000000 kernel: ================================================================================
AFAIR we didn't have ip_sockglue.c yet, did we? kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in net/ipv4/ip_sockglue.c:60:36 kernel: member access within misaligned address 00000000792184a3 for type 'struct iphdr' kernel: which requires 4 byte alignment kernel: CPU: 4 PID: 7862 Comm: chronyd Tainted: P O T 4.19.15-gentoo #2 kernel: Hardware name: ASUSTeK COMPUTER INC. G752VY/G752VY, BIOS G752VY.304 06/29/2017 kernel: Call Trace: kernel: dump_stack+0xa1/0x11b kernel: ubsan_epilogue+0x9/0x40 kernel: ubsan_type_mismatch_common+0x17b/0x190 kernel: __ubsan_handle_type_mismatch+0x43/0x60 kernel: ip_cmsg_recv_offset+0x8e3/0xa20 kernel: ? __sock_recv_ts_and_drops+0x92/0x370 kernel: udp_recvmsg+0x6c7/0xc30 kernel: ? import_iovec+0x50/0x2c0 kernel: inet_recvmsg+0x81/0x2b0 kernel: ___sys_recvmsg+0x10d/0x2a0 kernel: ? __sys_recvmmsg+0x145/0x5f0 kernel: __sys_recvmmsg+0x145/0x5f0 kernel: do_sys_recvmmsg+0xb7/0xd0 kernel: __x64_sys_recvmmsg+0x46/0x100 kernel: do_syscall_64+0x85/0x280 kernel: entry_SYSCALL_64_after_hwframe+0x49/0xbe kernel: RIP: 0033:0x7f1a7140306c kernel: Code: 89 4c 24 14 e8 15 d4 00 00 4c 8b 44 24 18 44 8b 54 24 14 41 89 c1 8b 54 24 10 48 8b 74 24 08 b8 2b 01 00 00 8b 7c 24 04 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 cf 89 44 24 04 e8 40 d4 00 00 8b 44 kernel: RSP: 002b:00007ffc42b070a0 EFLAGS: 00000293 ORIG_RAX: 000000000000012b kernel: RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f1a7140306c kernel: RDX: 0000000000000004 RSI: 0000562ab10139c0 RDI: 0000000000000004 kernel: RBP: 0000562ab10139c0 R08: 0000000000000000 R09: 0000000000000000 kernel: R10: 0000000000000040 R11: 0000000000000293 R12: 0000000000000004 kernel: R13: 0000000000000004 R14: 00007ffc42b073b0 R15: 0000000000000010 kernel: ================================================================================
(In reply to segmentation fault from comment #17) > Now, before I spend another day doing the above for kernel 4.20.2, which is > the latest one currently, I would like to know from you who are reading > this: do you have a *founded* reason to believe that those issues have been > taken care of in the 4.20.x kernels, or is it just a 'hope'? Did the lines > mentioned in the UBSAN messages change from 4.19.15 to 4.20.x? If not, just > trying new kernels is an exercise in futility. I think nobody here reading this knows for sure. But there is a chance that a newer kernel could have it fixed. I find it great that you want it to be fixed, but I'm afraid there is little that can be done on Gentoo side. These really seem like issues on the kernel side. Maybe you should try the latest vanilla kernel and then report on https://bugzilla.kernel.org or ask on their mailing list.
(In reply to Tomáš Mózes from comment #21) > I think nobody here reading this knows for sure. But there is a chance that > a newer kernel could have it fixed. After thinking deeply about this (well, no...actually, after having a walk along the river :-)), I am sure I can answer the question in the negative by applying pure logic: 1) According to https://www.linux.com/blog/2018/10/linux-kernel-419-long-term-support-usb-type-c-and-wifi-6 kernel 4.19 is a 'long-term support' (LTS) kernel. 2) According to the same article, an LTS kernel "will receive updates and patches to keep it safe and maintained for at least a couple of years". 3) Taking care of the UBSAN messages I reported here and in the 17 (didn't count...) other recent bug reports IS the kind of care one would expect for a kernel to be kept "safe and maintained" in the sense of 2). Therefore, IF those issues had been addressed in a later kernel (including, but not limited to the 4.20.x series), THEN they would have been backported to the latest 4.19 version, which I use. Given that this version still exhibits the reported undefined behaviour, it is quite safe to bet that the same is true for the latest kernels too, including 4.20.x. Pure logic. :-) > I find it great that you want it to be fixed, but I'm afraid there is > little that can be done on Gentoo side. These really seem like issues on the > kernel side. Maybe you should try the latest vanilla kernel and then report > on https://bugzilla.kernel.org or ask on their mailing list. And I am trying to avoid just that. I am sure somebody who is already subscribed to the list can put the 18 links in a message and point the kernel folks here. I don't expect Gentoo developers to resolve the issues, but I do expect them to forward the messages, if deemed necessary. It's the 'line of command', as I see it: I report to you, you report to the kernel developers. :-)
Just to let everyone know: all these messages are still there with kernel 4.19.18. One (almost) gets used to them...
UPDATE: kernel 4.19.19: The situation remains unchanged. Here is a summary of what I have seen in the kernel log so far (uptime: 12 hours, just a few xterms, vi, gvim and a browser open): kernel: UBSAN: Undefined behaviour in ./include/linux/etherdevice.h:139:17 kernel: UBSAN: Undefined behaviour in ./include/linux/tcp.h:35:11 kernel: UBSAN: Undefined behaviour in ./include/linux/unaligned/access_ok.h:50:17 kernel: UBSAN: Undefined behaviour in ./include/net/dsfield.h:18:12 kernel: UBSAN: Undefined behaviour in ./include/uapi/linux/byteorder/little_endian.h:58:9 kernel: UBSAN: Undefined behaviour in ./include/uapi/linux/swab.h:166:9 kernel: UBSAN: Undefined behaviour in ./include/uapi/linux/swab.h:179:9 kernel: UBSAN: Undefined behaviour in fs/xfs/libxfs/xfs_ialloc_btree.c:243:18 kernel: UBSAN: Undefined behaviour in net/core/dev.c:9480:2 kernel: UBSAN: Undefined behaviour in net/core/net_namespace.c:565:2 kernel: UBSAN: Undefined behaviour in net/ipv4/af_inet.c:1452:8 kernel: UBSAN: Undefined behaviour in net/ipv4/fib_frontend.c:292:21 kernel: UBSAN: Undefined behaviour in net/ipv4/igmp.c:1059:12 kernel: UBSAN: Undefined behaviour in net/ipv4/ip_input.c:281:19 kernel: UBSAN: Undefined behaviour in net/ipv4/ip_output.c:1573:41 kernel: UBSAN: Undefined behaviour in net/ipv4/ip_sockglue.c:60:36 kernel: UBSAN: Undefined behaviour in net/ipv4/netfilter/nf_log_ipv4.c:65:12 kernel: UBSAN: Undefined behaviour in net/ipv4/route.c:2157:23 kernel: UBSAN: Undefined behaviour in net/ipv4/tcp_input.c:3788:18 kernel: UBSAN: Undefined behaviour in net/ipv4/tcp_minisocks.c:107:46 kernel: UBSAN: Undefined behaviour in net/ipv4/tcp_minisocks.c:99:8 kernel: UBSAN: Undefined behaviour in net/ipv4/tcp_offload.c:229:7 kernel: UBSAN: Undefined behaviour in net/ipv4/udp.c:2365:8 kernel: UBSAN: Undefined behaviour in net/netfilter/nf_conntrack_proto_tcp.c:295:11 kernel: UBSAN: Undefined behaviour in net/unix/garbage.c:301:2 I have tried to report only unique messages (unique per filename and variable). Here are the UBSAN messages (only the first few lines per message shown): kernel: UBSAN: Undefined behaviour in net/ipv4/netfilter/nf_log_ipv4.c:65:12 kernel: member access within misaligned address 00000000bd659f19 for type 'const struct iphdr' kernel: which requires 4 byte alignment kernel: CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in net/ipv4/route.c:2157:23 kernel: member access within misaligned address 00000000014ae91b for type 'struct iphdr' kernel: which requires 4 byte alignment kernel: CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in net/ipv4/ip_input.c:281:19 kernel: member access within misaligned address 00000000014ae91b for type 'const struct iphdr' kernel: which requires 4 byte alignment kernel: CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in net/ipv4/igmp.c:1059:12 kernel: member access within misaligned address 00000000a5d61de4 for type 'struct igmphdr' kernel: which requires 4 byte alignment kernel: CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in ./include/linux/etherdevice.h:139:17 kernel: load of misaligned address 0000000030566dc9 for type 'const u64' kernel: which requires 8 byte alignment kernel: CPU: 1 PID: 8678 Comm: nmbd Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in ./include/uapi/linux/byteorder/little_endian.h:58:9 kernel: load of misaligned address 00000000d72d3c9b for type 'const __le32' kernel: which requires 4 byte alignment kernel: CPU: 2 PID: 8815 Comm: mkfs.ext4 Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in ./include/linux/unaligned/access_ok.h:50:17 kernel: store to misaligned address 0000000046bafe88 for type '__le64' kernel: which requires 8 byte alignment kernel: CPU: 2 PID: 8815 Comm: mkfs.ext4 Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in net/ipv4/udp.c:2365:8 kernel: member access within misaligned address 000000004eacf35e for type 'const struct iphdr' kernel: which requires 4 byte alignment kernel: CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in net/ipv4/fib_frontend.c:292:21 kernel: member access within misaligned address 00000000b54ed9ce for type 'struct iphdr' kernel: which requires 4 byte alignment kernel: CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in net/ipv4/ip_sockglue.c:60:36 kernel: member access within misaligned address 00000000b54ed9ce for type 'struct iphdr' kernel: which requires 4 byte alignment kernel: CPU: 1 PID: 7824 Comm: chronyd Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in net/unix/garbage.c:301:2 kernel: member access within misaligned address 00000000be41d9c7 for type 'struct unix_sock' kernel: which requires 64 byte alignment kernel: CPU: 7 PID: 9858 Comm: Gecko_IOThread Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in ./include/net/dsfield.h:18:12 kernel: member access within misaligned address 00000000f0e39fa3 for type 'const struct iphdr' kernel: which requires 4 byte alignment kernel: CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in ./include/linux/tcp.h:35:11 kernel: member access within misaligned address 000000007bd57029 for type 'const struct tcphdr' kernel: which requires 4 byte alignment kernel: CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in net/ipv4/tcp_input.c:3788:18 kernel: member access within misaligned address 000000007bd57029 for type 'const struct tcphdr' kernel: which requires 4 byte alignment kernel: CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in ./include/uapi/linux/swab.h:179:9 kernel: load of misaligned address 00000000038b9ec4 for type 'const __u32' kernel: which requires 4 byte alignment kernel: CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in net/netfilter/nf_conntrack_proto_tcp.c:295:11 kernel: member access within misaligned address 000000007a7dc5e2 for type 'const struct tcphdr' kernel: which requires 4 byte alignment kernel: CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in net/ipv4/af_inet.c:1452:8 kernel: member access within misaligned address 000000000a4035b5 for type 'const struct iphdr' kernel: which requires 4 byte alignment kernel: CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in net/ipv4/tcp_offload.c:229:7 kernel: load of misaligned address 000000003fb103e6 for type 'u32' kernel: which requires 4 byte alignment kernel: CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in net/ipv4/tcp_minisocks.c:99:8 kernel: member access within misaligned address 00000000f31187eb for type 'const struct tcphdr' kernel: which requires 4 byte alignment kernel: CPU: 4 PID: 9999 Comm: Web Content Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in net/ipv4/tcp_minisocks.c:107:46 kernel: member access within misaligned address 00000000f31187eb for type 'const struct tcphdr' kernel: which requires 4 byte alignment kernel: CPU: 4 PID: 9999 Comm: Web Content Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in net/ipv4/ip_output.c:1573:41 kernel: member access within misaligned address 00000000f31187eb for type 'struct tcphdr' kernel: which requires 4 byte alignment kernel: CPU: 4 PID: 9999 Comm: Web Content Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in net/core/dev.c:9480:2 kernel: member access within misaligned address 00000000d592c5a2 for type 'struct net_device' kernel: which requires 64 byte alignment kernel: CPU: 0 PID: 10358 Comm: kworker/u16:0 Tainted: P O T 4.19.19-gentoo #1 kernel: Workqueue: netns cleanup_net kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in net/core/net_namespace.c:565:2 kernel: member access within misaligned address 000000007f09d17e for type 'struct net' kernel: which requires 64 byte alignment kernel: CPU: 0 PID: 10358 Comm: kworker/u16:0 Tainted: P O T 4.19.19-gentoo #1 kernel: Workqueue: netns cleanup_net kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in fs/xfs/libxfs/xfs_ialloc_btree.c:243:18 kernel: member access within misaligned address 00000000d4997869 for type 'union xfs_btree_key' kernel: which requires 8 byte alignment kernel: CPU: 1 PID: 14360 Comm: mount Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================ kernel: UBSAN: Undefined behaviour in ./include/uapi/linux/swab.h:166:9 kernel: load of misaligned address 00000000b03fbf07 for type 'const __u16' kernel: which requires 2 byte alignment kernel: CPU: 1 PID: 14360 Comm: mount Tainted: P O T 4.19.19-gentoo #1 kernel: ================================================================================
Detection of undefined behavior via the UndefinedBehaviorSanitizer can be reported upstream at https://bugzilla.kernel.org
