From: Shuah Khan <shuah@kernel.org>
To: Sumit Semwal <sumit.semwal@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, linux-kselftest@vger.kernel.org
Cc: Brian Norris <computersforpeace@gmail.com>,
mcgrof@kernel.org, Kees Cook <keescook@chromium.org>,
Shuah Khan <shuah@kernel.org>
Subject: Re: LTS testing with latest kselftests - some failures
Date: Thu, 15 Jun 2017 12:30:04 -0600 [thread overview]
Message-ID: <757548e7-e7d6-9c0b-f094-7b838538fbbf@kernel.org> (raw)
In-Reply-To: <CAO_48GFNXyqTDN85y8FKLV3wj19JJ28sWXuX4Vex3LVzaxzGCw@mail.gmail.com>
Hi Sumit,
On 06/15/2017 11:56 AM, Sumit Semwal wrote:
> 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.
I will take a look the commit list your provided and see if it makes sense
to back-port. As we discussed earlier in this thread, fixes are something
that can be back-ported to include in the stable releases. Updates will not
be.
> 2. Bitmap test - test got added in 4.5, fails if test_bitmap.ko isn't present.
If you can send a patch to have it exit gracefully and change the message
to say unsupported feature, I can pull that into mainline can mark it for
stable inclusion if it qualifies.
>
> 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.
This is something I need to look at and consult with Security maintainers.
>
> For all the 3 listed above, we will try and update the tests to gracefully exit.
That is great.
>
>
> 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]
Hmm. I didn't notice this one. I will check and see what's going on there.
>
>
> 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.
Please cc me and linux-kselftest mailing list.
Thanks for reporting the problems.
>
>
> [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
>
>
thanks,
-- Shuah
next prev parent reply other threads:[~2017-06-15 18:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 17:56 LTS testing with latest kselftests - some failures Sumit Semwal
2017-06-15 18:30 ` Shuah Khan [this message]
2017-06-15 23:05 ` Alexander Alemayhu
2017-06-16 4:31 ` Sumit Semwal
2017-06-16 7:14 ` Alexander Alemayhu
2017-06-16 7:38 ` Sumit Semwal
2017-06-16 19:26 ` Alexander Alemayhu
2017-06-16 16:46 ` Luis R. Rodriguez
2017-06-16 19:29 ` Greg Kroah-Hartman
2017-06-16 19:47 ` Luis R. Rodriguez
2017-06-17 4:16 ` Greg Kroah-Hartman
2017-06-19 14:48 ` Luis R. Rodriguez
2017-06-19 14:55 ` Greg Kroah-Hartman
2017-06-19 17:32 ` Luis R. Rodriguez
2017-06-16 23:55 ` Fengguang Wu
2017-06-19 18:56 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=757548e7-e7d6-9c0b-f094-7b838538fbbf@kernel.org \
--to=shuah@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=stable@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).