linux-kernel - Re: [Test Failure Report] exec: Test failures in execveat

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, 14 Mar 2024 13:49:50 +0500
From: Muhammad Usama Anjum <usama.anjum@...labora.com>
To: Kees Cook <keescook@...omium.org>
Cc: Muhammad Usama Anjum <usama.anjum@...labora.com>,
 Eric Biederman <ebiederm@...ssion.com>, Shuah Khan <shuah@...nel.org>,
 Mark Brown <broonie@...nel.org>, linux-mm@...ck.org,
 linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
 "kernel@...labora.com" <kernel@...labora.com>
Subject: Re: [Test Failure Report] exec: Test failures in execveat

On 3/14/24 8:05 AM, Kees Cook wrote:
> On Mon, Mar 11, 2024 at 10:08:36PM +0500, Muhammad Usama Anjum wrote:
>> On 3/8/24 1:39 AM, Kees Cook wrote:
>>> On Thu, Mar 07, 2024 at 02:22:27PM +0500, Muhammad Usama Anjum wrote:
>>>> I've tested this patch. Still getting same failures.
>>>
>>> Okay, thanks for testing!
>>>
>>> What environment are you testing under? It would seem like some unexpected
>>> userspace conditions exist that the test isn't prepared for. (I was able
>>> to reproduce one error with /bin/dash, for example, but not the others,
>>> so something must be different in the set up.)
>> I'm testing on Debian Bookworm with v6.1, v6.7 and next-20240304 kernels.
>> I've tested it on another VM which is also Debian Bookworm. The default
>> shell is dash on Debian as well.
> 
> Do you know which kernel version this _passes_ on? I haven't been able
> to find when this actually returned the expected values...
I'd tried to find a kernel on which it used to pass i.e., I rewinded the
kernel to the last change in this test. But still it was failing on that.
Not sure if the test is wrong or the environment is making the test to
output wrong values.

> 

-- 
BR,
Muhammad Usama Anjum