linux-kernel - Re: [lkp-robot] [selftests] 26e500fe62: kernel_selftests.mqueue.mq_open

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 28 Sep 2017 09:22:52 -0600
From:   Shuah Khan <shuahkh@....samsung.com>
To:     kernel test robot <xiaolong.ye@...el.com>
Cc:     LKML <linux-kernel@...r.kernel.org>, lkp@...org,
        Shuah Khan <shuahkh@....samsung.com>
Subject: Re: [lkp-robot] [selftests] 26e500fe62:
 kernel_selftests.mqueue.mq_open_tests.fail

On 09/28/2017 09:15 AM, Shuah Khan wrote:
> On 09/28/2017 01:58 AM, kernel test robot wrote:
>>
>> FYI, we noticed the following commit:
>>
>> commit: 26e500fe628e28f2e93d397014beeb9c213d91e9 ("selftests: mqueue: Use full path to run tests from Makefile")
>> https://git.kernel.org/cgit/linux/kernel/git/shuah/linux-kselftest.git fixes
>>
>> in testcase: kernel_selftests
>> with following parameters:
>>
>>
>> test-description: The kernel contains a set of "self tests" under the tools/testing/selftests/ directory. These are intended to be small unit tests to exercise individual code paths in the kernel.
>> test-url: https://www.kernel.org/doc/Documentation/kselftest.txt
>>
>>
>> on test machine: 88 threads Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz with 64G memory
>>
>> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>>
>>
>>
>> 2017-09-27 18:35:28 make run_tests -C mqueue
>> make: Entering directory '/usr/src/linux-selftests-x86_64-rhel-7.2-26e500fe628e28f2e93d397014beeb9c213d91e9/tools/testing/selftests/mqueue'
>> gcc -O2    mq_open_tests.c -lrt -lpthread -lpopt -o /usr/src/linux-selftests-x86_64-rhel-7.2-26e500fe628e28f2e93d397014beeb9c213d91e9/tools/testing/selftests/mqueue/mq_open_tests
>> gcc -O2    mq_perf_tests.c -lrt -lpthread -lpopt -o /usr/src/linux-selftests-x86_64-rhel-7.2-26e500fe628e28f2e93d397014beeb9c213d91e9/tools/testing/selftests/mqueue/mq_perf_tests
>> /usr/src/linux-selftests-x86_64-rhel-7.2-26e500fe628e28f2e93d397014beeb9c213d91e9/tools/testing/selftests/mqueue/mq_open_tests /test1 || echo "selftests: mq_open_tests [FAIL]"
>> /usr/src/linux-selftests-x86_64-rhel-7.2-26e500fe628e28f2e93d397014beeb9c213d91e9/tools/testing/selftests/mqueue//mq_perf_tests || echo "selftests: mq_perf_tests [FAIL]"
>>
>> Initial system state:
>> 	Using queue path:		/test1
>> 	RLIMIT_MSGQUEUE(soft):		819200
>> 	RLIMIT_MSGQUEUE(hard):		819200
>> 	Maximum Message Size:		8192
>> 	Maximum Queue Size:		10
>> 	Default Message Size:		8192
>> 	Default Queue Size:		10
>>
>> Adjusted system state for testing:
>> 	RLIMIT_MSGQUEUE(soft):		819200
>> 	RLIMIT_MSGQUEUE(hard):		819200
>> 	Maximum Message Size:		8192
>> 	Maximum Queue Size:		10
>> 	Default Message Size:		8192
>> 	Default Queue Size:		10
>>
>>
> 
> Will you be able to send me the results without this change.
> I am unable to figure out the difference.

Ah I see. You are talking about the difference in the adjusted
system state. That is weird. The only change this patch makes
it the test path.

I will look into this further.

thanks,
-- Shuah