From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] insmod01_sh test from commands test suite will make cve-2017-17053 test fail
Date: Wed, 5 Jun 2019 09:02:29 +0200 [thread overview]
Message-ID: <20190605070228.GA778@rei.lan> (raw)
In-Reply-To: <CAMy_GT-80RtX=qkXJ0NYN-3eY_N+MiH5Xq5iPGm41y=d-n3CAA@mail.gmail.com>
Hi!
> Yes you're right, the insmod test is not the cause here.
>
> I found it's the block_dev test from kernel_misc, the ltp_block_dev
> module insertion will first set the taint flag to 12288:
> $ sudo insmod ltp_block_dev.ko
> $ cat /proc/sys/kernel/tainted
> 12288
>
> But the test will generate kernel warnings and make it 12800
> $ sudo rmmod ltp_block_dev
> $ sudo ./block_dev
> block_dev 1 TPASS : Test-case '1'
> block_dev 2 TPASS : Test-case '2'
> block_dev 3 TPASS : Test-case '3'
> block_dev 4 TPASS : Test-case '4'
> block_dev 5 TPASS : Test-case '5'
> block_dev 6 TPASS : Test-case '6'
> block_dev 7 TPASS : Test-case '7'
> $ cat /proc/sys/kernel/tainted
> 12800
>
> 12800 = 0011001000000000
> The W flag is here.
>
> Traces could be found in dmesg:
> https://pastebin.ubuntu.com/p/gp9ZDHNj6J/
Looking at the test and at the kernel source the test is triggering
exactly the condition it's supposed to to trigger and the warning is to
be expected.
I guess that the best solution would be running the kernel_misc
testcases separately from the rest.
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2019-06-05 7:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 7:41 [LTP] insmod01_sh test from commands test suite will make cve-2017-17053 test fail Po-Hsu Lin
2019-05-31 8:32 ` Cyril Hrubis
2019-05-31 9:25 ` Cyril Hrubis
2019-05-31 9:43 ` Cyril Hrubis
2019-06-04 11:44 ` Po-Hsu Lin
2019-06-05 7:02 ` Cyril Hrubis [this message]
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=20190605070228.GA778@rei.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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