From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: Kees Cook <keescook@chromium.org>
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
Eric Biederman <ebiederm@xmission.com>,
Shuah Khan <shuah@kernel.org>, Mark Brown <broonie@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
"kernel@collabora.com" <kernel@collabora.com>
Subject: Re: [Test Failure Report] exec: Test failures in execveat
Date: Mon, 11 Mar 2024 22:08:36 +0500 [thread overview]
Message-ID: <cf98ff2f-66a8-4800-855f-5c03c952b514@collabora.com> (raw)
In-Reply-To: <202403071238.AC7BD90@keescook>
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.
>
> -Kees
>
--
BR,
Muhammad Usama Anjum
next prev parent reply other threads:[~2024-03-11 17:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 14:20 [Test Failure Report] exec: Test failures in execveat Muhammad Usama Anjum
2024-03-05 21:00 ` Kees Cook
2024-03-07 9:22 ` Muhammad Usama Anjum
2024-03-07 20:39 ` Kees Cook
2024-03-11 17:08 ` Muhammad Usama Anjum [this message]
2024-03-13 5:23 ` Kees Cook
2024-03-14 3:05 ` Kees Cook
2024-03-14 8:49 ` Muhammad Usama Anjum
-- strict thread matches above, loose matches on Subject: below --
2024-03-19 11:17 Khannanov Lenar
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=cf98ff2f-66a8-4800-855f-5c03c952b514@collabora.com \
--to=usama.anjum@collabora.com \
--cc=broonie@kernel.org \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuah@kernel.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