linux-kernel - Re: [PATCH] selftests: sched: add sched as a default selftest target

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] [thread-next>] [day] [month] [year] [list]

Message-ID:
 <CO1PR10MB47051B268FCBD44E24B281439BC72@CO1PR10MB4705.namprd10.prod.outlook.com>
Date: Fri, 21 Feb 2025 04:21:06 +0000
From: Chris Hyser <chris.hyser@...cle.com>
To: Sinadin Shan <sinadin.shan@...cle.com>,
        Shrikanth Hegde
	<sshegde@...ux.ibm.com>
CC: "linux-kselftest@...r.kernel.org" <linux-kselftest@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "shuah@...nel.org" <shuah@...nel.org>
Subject: Re: [PATCH] selftests: sched: add sched as a default selftest target

From: Sinadin Shan <sinadin.shan@...cle.com>
Sent: Thursday, February 20, 2025 11:23 AM
To: Chris Hyser; Shrikanth Hegde
Cc: linux-kselftest@...r.kernel.org; linux-kernel@...r.kernel.org; shuah@...nel.org
Subject: Re: [PATCH] selftests: sched: add sched as a default selftest target

>> I guess my question is what if SCHED_CORE was supposed to be configed into
>> the test kernel?  Silently burying the error might be bad. I'm not strongly tied to
>> that, just looking for opinions. At the same time, if you put the orig change in,
>> people w/o SCHED_CORE on will start seeing "failures" they didn't see before,
>> yes? and that seems bad.
>
> Yes, that seems bad as rightly pointed out by Shrikant. I have a patch
> that does the above mentioned skip, and if skipping is a right option to
> take here I can send it in the next version.

If that is the plan, I prefer to fix it myself.

-chrish