Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753097AbdFOR5X (ORCPT ); Thu, 15 Jun 2017 13:57:23 -0400 Received: from mail-wr0-f177.google.com ([209.85.128.177]:34903 "EHLO mail-wr0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753071AbdFOR5V (ORCPT ); Thu, 15 Jun 2017 13:57:21 -0400 MIME-Version: 1.0 From: Sumit Semwal Date: Thu, 15 Jun 2017 23:26:53 +0530 Message-ID: Subject: LTS testing with latest kselftests - some failures To: Greg Kroah-Hartman , shuah@kernel.org, LKML , stable@vger.kernel.org, linux-kselftest@vger.kernel.org Cc: Brian Norris , mcgrof@kernel.org, Kees Cook Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1828 Lines: 47 Hello Greg, Shuah, While testing 4.4.y and 4.9.y LTS kernels with latest kselftest, we found a couple more test failures due to test-kernel mismatch: 1. firmware tests: - linux 4.5 [1] and 4.10 [2] added a few updates to tests, and related updates to lib/test_firmware.c to improve the tests. Stable-4.4 misses these patches to lib/test_firmware.c. Stable 4.9 misses the second update. 2. Bitmap test - test got added in 4.5, fails if test_bitmap.ko isn't present. 3. 'seccomp ptrace hole closure' patches got added in 4.7 [3] - feature and test together. - This one also seems like a security hole being closed, and the 'feature' could be a candidate for stable backports, but Arnd tried that, and it was quite non-trivial. So perhaps we'll need some help from the subsystem developers here. For all the 3 listed above, we will try and update the tests to gracefully exit. 4. bpf tests: These seem to have build failures in mainline as well - I also tried to build kselftest-next, but a simple 'make -C tools/testing/selftests/bpf' seems to error out. Are there any special instructions to build these? [I tried x86_64, arm64 cross-compile on x86_64] I will also individually request subsystem authors / mailing lists for each of these towards help in improving these tests if required, but wanted to use this thread as a converging point. Thanks and Best regards, Sumit. [1]: https://lkml.org/lkml/2015/12/8/816 Patches added via [1]: eb910947c82f (test: firmware_class: add asynchronous request trigger) be4a1326d12c (test: firmware_class: use kstrndup() where appropriate) 47e0bbb7fa98 (test: firmware_class: report errors properly on failure) [2]: https://lkml.org/lkml/2017/1/23/440 Patch added via [2]: 061132d2b9c9 (test_firmware: add test custom fallback trigger) [3]: https://lkml.org/lkml/2016/6/9/627