Hello,
We ran automated tests on a patchset that was proposed for merging into this kernel tree. The patches were applied to:
Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git Commit: d3da1f09fff2 - Linux 5.0.10
The results of these automated tests are provided below.
Overall result: FAILED (see details below) Merge: OK Compile: OK Tests: FAILED
One or more kernel tests failed:
aarch64:
We hope that these logs can help you find the problem quickly. For the full detail on our testing procedures, please scroll to the bottom of this message.
Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective.
,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________
Merge testing -------------
We cloned this repository and checked out the following commit:
Repo: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git Commit: d3da1f09fff2 - Linux 5.0.10
We then merged the patchset with `git am`:
netfilter-nf_tables-bogus-ebusy-when-deleting-set-af.patch netfilter-nf_tables-bogus-ebusy-in-helper-removal-fr.patch intel_th-gth-fix-an-off-by-one-in-output-unassigning.patch powerpc-vdso32-fix-clock_monotonic-on-ppc64.patch alsa-hda-realtek-move-to-act_init-state.patch fs-proc-proc_sysctl.c-fix-a-null-pointer-dereference.patch block-bfq-fix-use-after-free-in-bfq_bfqq_expire.patch cifs-fix-memory-leak-in-smb2_read.patch cifs-fix-page-reference-leak-with-readv-writev.patch cifs-do-not-attempt-cifs-operation-on-smb2-rename-error.patch tracing-fix-a-memory-leak-by-early-error-exit-in-trace_pid_write.patch tracing-fix-buffer_ref-pipe-ops.patch crypto-xts-fix-atomic-sleep-when-walking-skcipher.patch crypto-lrw-fix-atomic-sleep-when-walking-skcipher.patch gpio-eic-sprd-fix-incorrect-irq-type-setting-for-the-sync-eic.patch zram-pass-down-the-bvec-we-need-to-read-into-in-the-work-struct.patch lib-kconfig.debug-fix-build-error-without-config_block.patch mips-scall64-o32-fix-indirect-syscall-number-load.patch trace-fix-preempt_enable_no_resched-abuse.patch mm-do-not-boost-watermarks-to-avoid-fragmentation-for-the-discontig-memory-model.patch arm64-mm-ensure-tail-of-unaligned-initrd-is-reserved.patch ib-rdmavt-fix-frwr-memory-registration.patch rdma-mlx5-do-not-allow-the-user-to-write-to-the-clock-page.patch rdma-mlx5-use-rdma_user_map_io-for-mapping-bar-pages.patch rdma-ucontext-fix-regression-with-disassociate.patch sched-numa-fix-a-possible-divide-by-zero.patch ceph-only-use-d_name-directly-when-parent-is-locked.patch ceph-ensure-d_name-stability-in-ceph_dentry_hash.patch ceph-fix-ci-i_head_snapc-leak.patch nfsd-don-t-release-the-callback-slot-unless-it-was-actually-held.patch nfsd-wake-waiters-blocked-on-file_lock-before-deleting-it.patch nfsd-wake-blocked-file-lock-waiters-before-sending-callback.patch sunrpc-don-t-mark-uninitialised-items-as-valid.patch perf-x86-intel-update-kbl-package-c-state-events-to-also-include-pc8-pc9-pc10-counters.patch input-synaptics-rmi4-write-config-register-values-to-the-right-offset.patch vfio-type1-limit-dma-mappings-per-container.patch dmaengine-sh-rcar-dmac-with-cyclic-dma-residue-0-is-valid.patch dmaengine-sh-rcar-dmac-fix-glitch-in-dmaengine_tx_status.patch dmaengine-mediatek-cqdma-fix-wrong-register-usage-in-mtk_cqdma_start.patch arm-8857-1-efi-enable-cp15-dmb-instructions-before-cleaning-the-cache.patch powerpc-mm-radix-make-radix-require-hugetlb_page.patch drm-vc4-fix-memory-leak-during-gpu-reset.patch drm-ttm-fix-re-init-of-global-structures.patch revert-drm-i915-fbdev-actually-configure-untiled-displays.patch drm-vc4-fix-compilation-error-reported-by-kbuild-test-bot.patch usb-add-new-usb-lpm-helpers.patch usb-consolidate-lpm-checks-to-avoid-enabling-lpm-twice.patch ext4-fix-some-error-pointer-dereferences.patch loop-do-not-print-warn-message-if-partition-scan-is-successful.patch tipc-handle-the-err-returned-from-cmd-header-function.patch slip-make-slhc_free-silently-accept-an-error-pointer.patch workqueue-try-to-catch-flush_work-without-init_work.patch binder-fix-handling-of-misaligned-binder-object.patch sched-deadline-correctly-handle-active-0-lag-timers.patch mac80211_hwsim-calculate-if_combination.max_interfaces.patch nfs-forbid-setting-af_inet6-to-struct-sockaddr_in-sin_family.patch netfilter-ebtables-config_compat-drop-a-bogus-warn_on.patch fm10k-fix-a-potential-null-pointer-dereference.patch tipc-check-bearer-name-with-right-length-in-tipc_nl_compat_bearer_enable.patch tipc-check-link-name-with-right-length-in-tipc_nl_compat_link_set.patch net-netrom-fix-error-cleanup-path-of-nr_proto_init.patch net-rds-check-address-length-before-reading-address-family.patch rxrpc-fix-race-condition-in-rxrpc_input_packet.patch pin-iocb-through-aio.patch aio-fold-lookup_kiocb-into-its-sole-caller.patch aio-keep-io_event-in-aio_kiocb.patch aio-store-event-at-final-iocb_put.patch fix-aio_poll-races.patch x86-retpolines-raise-limit-for-generating-indirect-calls-from-switch-case.patch x86-retpolines-disable-switch-jump-tables-when-retpolines-are-enabled.patch rdma-fix-build-errors-on-s390-and-mips-due-to-bad-zero_page-use.patch ipv4-add-sanity-checks-in-ipv4_link_failure.patch ipv4-set-the-tcp_min_rtt_wlen-range-from-0-to-one-day.patch mlxsw-spectrum-fix-autoneg-status-in-ethtool.patch net-mlx5e-ethtool-remove-unsupported-sfp-eeprom-high-pages-query.patch net-rds-exchange-of-8k-and-1m-pool.patch net-rose-fix-unbound-loop-in-rose_loopback_timer.patch net-stmmac-move-stmmac_check_ether_addr-to-driver-probe.patch net-tls-fix-refcount-adjustment-in-fallback.patch stmmac-pci-adjust-iot2000-matching.patch team-fix-possible-recursive-locking-when-add-slaves.patch net-socionext-replace-napi_alloc_frag-with-the-netdev-variant-on-init.patch net-ncsi-handle-overflow-when-incrementing-mac-address.patch mlxsw-pci-reincrease-pci-reset-timeout.patch mlxsw-spectrum-put-mc-tcs-into-dwrr-mode.patch net-mlx5e-fix-the-max-mtu-check-in-case-of-xdp.patch net-mlx5e-fix-use-after-free-after-xdp_return_frame.patch net-tls-avoid-potential-deadlock-in-tls_set_device_offload_rx.patch net-tls-don-t-leak-iv-and-record-seq-when-offload-fails.patch
Compile testing ---------------
We compiled the kernel for 4 architectures:
aarch64: build options: -j20 INSTALL_MOD_STRIP=1 targz-pkg configuration: https://artifacts.cki-project.org/builds/aarch64/kernel-stable_queue-aarch64... kernel build: https://artifacts.cki-project.org/builds/aarch64/kernel-stable_queue-aarch64...
ppc64le: build options: -j20 INSTALL_MOD_STRIP=1 targz-pkg configuration: https://artifacts.cki-project.org/builds/ppc64le/kernel-stable_queue-ppc64le... kernel build: https://artifacts.cki-project.org/builds/ppc64le/kernel-stable_queue-ppc64le...
s390x: build options: -j20 INSTALL_MOD_STRIP=1 targz-pkg configuration: https://artifacts.cki-project.org/builds/s390x/kernel-stable_queue-s390x-ac5... kernel build: https://artifacts.cki-project.org/builds/s390x/kernel-stable_queue-s390x-ac5...
x86_64: build options: -j20 INSTALL_MOD_STRIP=1 targz-pkg configuration: https://artifacts.cki-project.org/builds/x86_64/kernel-stable_queue-x86_64-a... kernel build: https://artifacts.cki-project.org/builds/x86_64/kernel-stable_queue-x86_64-a...
Hardware testing ----------------
We booted each kernel and ran the following tests:
aarch64: ✅ Boot test [0] ❎ LTP lite [1] ✅ Loopdev Sanity [2] ✅ AMTU (Abstract Machine Test Utility) [3] ✅ Ethernet drivers sanity [4] ✅ httpd: mod_ssl smoke sanity [5] ✅ iotop: sanity [6] ✅ tuned: tune-processes-through-perf [7] ✅ Usex - version 1.9-29 [8] ✅ lvm thinp sanity [9] ✅ Boot test [0] ✅ xfstests: ext4 [10] ✅ xfstests: xfs [10] 🚧 ✅ Networking route: pmtu [11] 🚧 ✅ audit: audit testsuite test [12] 🚧 ✅ stress: stress-ng [13]
ppc64le: ✅ Boot test [0] ✅ LTP lite [1] ✅ Loopdev Sanity [2] ✅ AMTU (Abstract Machine Test Utility) [3] ✅ Ethernet drivers sanity [4] ✅ httpd: mod_ssl smoke sanity [5] ✅ iotop: sanity [6] ✅ tuned: tune-processes-through-perf [7] ✅ Usex - version 1.9-29 [8] ✅ lvm thinp sanity [9] ✅ Boot test [0] ✅ xfstests: ext4 [10] ✅ xfstests: xfs [10] 🚧 ✅ Networking route: pmtu [11] 🚧 ✅ audit: audit testsuite test [12] 🚧 ✅ selinux-policy: serge-testsuite [14] 🚧 ✅ stress: stress-ng [13]
s390x:
x86_64: ✅ Boot test [0] ✅ xfstests: ext4 [10] ✅ xfstests: xfs [10] ✅ Boot test [0] ✅ LTP lite [1] ✅ Loopdev Sanity [2] ✅ AMTU (Abstract Machine Test Utility) [3] ✅ Ethernet drivers sanity [4] ✅ httpd: mod_ssl smoke sanity [5] ✅ iotop: sanity [6] ✅ tuned: tune-processes-through-perf [7] ✅ Usex - version 1.9-29 [8] ✅ lvm thinp sanity [9] 🚧 ✅ Networking route: pmtu [11] 🚧 ✅ audit: audit testsuite test [12] 🚧 ✅ selinux-policy: serge-testsuite [14] 🚧 ✅ stress: stress-ng [13]
Test source: [0]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution/... [1]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution/... [2]: https://github.com/CKI-project/tests-beaker/archive/master.zip#filesystems/l... [3]: https://github.com/CKI-project/tests-beaker/archive/master.zip#misc/amtu [4]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/d... [5]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/http... [6]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/ioto... [7]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/tune... [8]: https://github.com/CKI-project/tests-beaker/archive/master.zip#standards/use... [9]: https://github.com/CKI-project/tests-beaker/archive/master.zip#storage/lvm/t... [10]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/filesystems/... [11]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/r... [12]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/audi... [13]: https://github.com/CKI-project/tests-beaker/archive/master.zip#stress/stress... [14]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/packages/sel...
Waived tests (marked with 🚧) ----------------------------- This test run included waived tests. Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed.
On 4/30/19 7:32 AM, CKI Project wrote:
aarch64: ✅ Boot test [0] ❎ LTP lite [1] ✅ Loopdev Sanity [2] ✅ AMTU (Abstract Machine Test Utility) [3] ✅ Ethernet drivers sanity [4] ✅ httpd: mod_ssl smoke sanity [5] ✅ iotop: sanity [6] ✅ tuned: tune-processes-through-perf [7] ✅ Usex - version 1.9-29 [8] ✅ lvm thinp sanity [9] ✅ Boot test [0] ✅ xfstests: ext4 [10] ✅ xfstests: xfs [10] 🚧 ✅ Networking route: pmtu [11] 🚧 ✅ audit: audit testsuite test [12] 🚧 ✅ stress: stress-ng [13]
All of the tests look fine for this build, but the aarch64 test failed on mtest06 in LTP:
<<<test_start>>> tag=mtest06 stime=1556617569 cmdline=" mmap1" contacts="" analysis=exit <<<test_output>>> tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s tst_test.c:1085: INFO: Timeout per run is 0h 03m 00s mmap1.c:234: INFO: [3] mapped: 20000, sigsegv hit: 2864, threads spawned: 8 mmap1.c:237: INFO: [3] repeated_reads: 0, data_matched: 17590074 mmap1.c:234: INFO: [6] mapped: 50000, sigsegv hit: 5296, threads spawned: 20 mmap1.c:237: INFO: [6] repeated_reads: 322, data_matched: 45330029 Test timeouted, sending SIGKILL! tst_test.c:1125: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1126: BROK: Test killed! (timeout?) Summary: passed 0 failed 0 skipped 0 warnings 0 <<<execution_status>>> initiation_status="ok" duration=180 termination_type=exited termination_id=2 corefile=no cutime=984 cstime=17098 <<<test_end>>>
This could be due to a slow host on our side and we're still taking a look. I figured that sharing all of the results would be helpful while we investigate. :)
-- Major Hayden
Hello CKI folks,
A minor nit: the icon added before the subject text gets filtered out on the textual email clients most of us use, and ends up appearing (at least for me) as 3 spaces that cause much annoyance since it gets confused with mail threading.
I'll work around that by filtering that thingie out using email rules, but maybe we can avoid sending it out for everyone? :)
-- Thanks, Sasha
On Tue, Apr 30, 2019 at 09:03:31AM -0400, Sasha Levin wrote:
Hello CKI folks,
A minor nit: the icon added before the subject text gets filtered out on the textual email clients most of us use, and ends up appearing (at least for me) as 3 spaces that cause much annoyance since it gets confused with mail threading.
Really? It's just a "normal" emoji character, perhaps you need a better email client or terminal window? :)
What are you using that you can't see this in a terminal?
On Tue, Apr 30, 2019 at 03:27:00PM +0200, Greg KH wrote:
On Tue, Apr 30, 2019 at 09:03:31AM -0400, Sasha Levin wrote:
Hello CKI folks,
A minor nit: the icon added before the subject text gets filtered out on the textual email clients most of us use, and ends up appearing (at least for me) as 3 spaces that cause much annoyance since it gets confused with mail threading.
Really? It's just a "normal" emoji character, perhaps you need a better email client or terminal window? :)
What are you using that you can't see this in a terminal?
Um, mutt on xterm...
On Tue, Apr 30, 2019 at 09:41:59AM -0400, Sasha Levin wrote:
On Tue, Apr 30, 2019 at 03:27:00PM +0200, Greg KH wrote:
On Tue, Apr 30, 2019 at 09:03:31AM -0400, Sasha Levin wrote:
Hello CKI folks,
A minor nit: the icon added before the subject text gets filtered out on the textual email clients most of us use, and ends up appearing (at least for me) as 3 spaces that cause much annoyance since it gets confused with mail threading.
Really? It's just a "normal" emoji character, perhaps you need a better email client or terminal window? :)
What are you using that you can't see this in a terminal?
Um, mutt on xterm...
Use a "modern" terminal program please, that's the problem here. I just tried 4 different ones (gnome-terminal, terminology, tilix, and kitty), and they all worked just fine.
With mutt :)
thanks,
greg k-h
On 4/30/19 9:01 AM, Greg KH wrote:
On Tue, Apr 30, 2019 at 09:41:59AM -0400, Sasha Levin wrote:
On Tue, Apr 30, 2019 at 03:27:00PM +0200, Greg KH wrote:
On Tue, Apr 30, 2019 at 09:03:31AM -0400, Sasha Levin wrote:
Hello CKI folks,
A minor nit: the icon added before the subject text gets filtered out on the textual email clients most of us use, and ends up appearing (at least for me) as 3 spaces that cause much annoyance since it gets confused with mail threading.
Really? It's just a "normal" emoji character, perhaps you need a better email client or terminal window? :)
What are you using that you can't see this in a terminal?
Um, mutt on xterm...
Use a "modern" terminal program please, that's the problem here. I just tried 4 different ones (gnome-terminal, terminology, tilix, and kitty), and they all worked just fine.
With mutt :)
We can change the email format very easily. If removing the emoji in the subject line would be better, that's a really quick change for us.
Our hope was that it would make it easier to identify automated CI results and make it easier to know the feedback when you're looking at a lot of email threads.
-- Major Hayden
On Tue, Apr 30, 2019 at 10:17:17AM -0500, Major Hayden wrote:
On 4/30/19 9:01 AM, Greg KH wrote:
On Tue, Apr 30, 2019 at 09:41:59AM -0400, Sasha Levin wrote:
On Tue, Apr 30, 2019 at 03:27:00PM +0200, Greg KH wrote:
On Tue, Apr 30, 2019 at 09:03:31AM -0400, Sasha Levin wrote:
Hello CKI folks,
A minor nit: the icon added before the subject text gets filtered out on the textual email clients most of us use, and ends up appearing (at least for me) as 3 spaces that cause much annoyance since it gets confused with mail threading.
Really? It's just a "normal" emoji character, perhaps you need a better email client or terminal window? :)
What are you using that you can't see this in a terminal?
Um, mutt on xterm...
Use a "modern" terminal program please, that's the problem here. I just tried 4 different ones (gnome-terminal, terminology, tilix, and kitty), and they all worked just fine.
With mutt :)
We can change the email format very easily. If removing the emoji in the subject line would be better, that's a really quick change for us.
Our hope was that it would make it easier to identify automated CI results and make it easier to know the feedback when you're looking at a lot of email threads.
I thought this was an issue for more people than just me. I'll just use a newer terminal emulator :)
-- Thanks, Sasha
On 2019-04-30 11:58 -0400, Sasha Levin wrote:
On Tue, Apr 30, 2019 at 10:17:17AM -0500, Major Hayden wrote:
On 4/30/19 9:01 AM, Greg KH wrote:
On Tue, Apr 30, 2019 at 09:41:59AM -0400, Sasha Levin wrote:
On Tue, Apr 30, 2019 at 03:27:00PM +0200, Greg KH wrote:
On Tue, Apr 30, 2019 at 09:03:31AM -0400, Sasha Levin wrote:
Hello CKI folks,
A minor nit: the icon added before the subject text gets filtered out on the textual email clients most of us use, and ends up appearing (at least for me) as 3 spaces that cause much annoyance since it gets confused with mail threading.
If you see 3 spaces rather than just one, you probably use a single-byte locale (e.g. 'C'), rather than a UTF-8 one.
Really? It's just a "normal" emoji character, perhaps you need a better email client or terminal window? :)
What are you using that you can't see this in a terminal?
Um, mutt on xterm...
Use a "modern" terminal program please, that's the problem here. I just tried 4 different ones (gnome-terminal, terminology, tilix, and kitty), and they all worked just fine.
With mutt :)
We can change the email format very easily. If removing the emoji in the subject line would be better, that's a really quick change for us.
Our hope was that it would make it easier to identify automated CI results and make it easier to know the feedback when you're looking at a lot of email threads.
I thought this was an issue for more people than just me. I'll just use a newer terminal emulator :)
Or configure xterm correctly. The '❎'emoji displays just fine under "LC_ALL=en_US.UTF-8 xterm -fa DejaVuSansMono" (tested with xterm 344).
Cheers, Sven
linux-stable-mirror@lists.linaro.org