ltp.lists.linux.it archive mirror
 help / color / mirror / Atom feed
From: Martin Doucha <mdoucha@suse.cz>
To: David Hildenbrand <david@redhat.com>, 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:25:38 +0100	[thread overview]
Message-ID: <af63ed9a-7108-fd19-fe2c-4b56be85d068@suse.cz> (raw)
In-Reply-To: <da91a3a8-4609-c128-1c73-8b35dfb2b7c9@redhat.com>

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.

-- 
Martin Doucha   mdoucha@suse.cz
QA Engineer for Software Maintenance
SUSE LINUX, s.r.o.
CORSO IIa
Krizikova 148/34
186 00 Prague 8
Czech Republic


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-11-25 10:25 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 [this message]
2022-11-25 10:29         ` David Hildenbrand
2022-11-25 10:39           ` Petr Vorel
2022-11-25 10:42             ` David Hildenbrand
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=af63ed9a-7108-fd19-fe2c-4b56be85d068@suse.cz \
    --to=mdoucha@suse.cz \
    --cc=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;
as well as URLs for NNTP newsgroup(s).