From: David Hildenbrand <david@redhat.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] security/dirtyc0w_shmem: Add new test for CVE-2022-2590
Date: Fri, 25 Nov 2022 11:42:32 +0100 [thread overview]
Message-ID: <0b5441ef-53cf-a540-cfbd-998629a6d349@redhat.com> (raw)
In-Reply-To: <Y4CbcQhk/UMkpfEX@pevik>
On 25.11.22 11:39, Petr Vorel wrote:
>> On 25.11.22 11:25, Martin Doucha wrote:
>>> On 25. 11. 22 11:20, David Hildenbrand wrote:
>>>> See my other mail, it's the case on all instances that pass NULL (and I
>>>> don't really see the need to do this when working with NULL.
>
>>> NULL may be defined as simple integer 0. When int is 32bit and pointers
>>> 64bit, this will cause trouble in variadic functions such as execlp().
>>> You do not need to remind us that LTP tests have lots of bugs, we know.
>
>> I can send a fixup patch for all these instances.
>
> Thank you!
The list of SAFE_EXEC* was fairly short, now I discovered manual execl*
usage... let me get a patch ready to fix all these :)
--
Thanks,
David / dhildenb
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-11-25 10:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 10:35 [LTP] [PATCH v2] security/dirtyc0w_shmem: Add new test for CVE-2022-2590 David Hildenbrand
2022-11-24 22:13 ` Petr Vorel
2022-11-25 9:53 ` Martin Doucha
2022-11-25 10:06 ` Petr Vorel
2022-11-25 10:20 ` David Hildenbrand
2022-11-25 10:25 ` Martin Doucha
2022-11-25 10:29 ` David Hildenbrand
2022-11-25 10:39 ` Petr Vorel
2022-11-25 10:42 ` David Hildenbrand [this message]
2022-11-25 10:17 ` David Hildenbrand
2022-11-25 14:22 ` Cyril Hrubis
2022-11-25 14:26 ` Martin Doucha
2022-11-25 14:35 ` Cyril Hrubis
2022-11-25 10:37 ` Martin Doucha
2022-11-25 10:39 ` Petr Vorel
2022-11-25 10:40 ` David Hildenbrand
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=0b5441ef-53cf-a540-cfbd-998629a6d349@redhat.com \
--to=david@redhat.com \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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