From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1 1/1] runtest/cve: Add some existing CVE tests to runtest file
Date: Tue, 20 Jun 2023 23:08:26 +0200 [thread overview]
Message-ID: <20230620210826.GB334441@pevik> (raw)
In-Reply-To: <CAEemH2doFsjjQwDA2P_-_vDrFSBtNoCXLXh3U__3W6jED4mhTw@mail.gmail.com>
Hi Li, all,
...
> > +cve-2017-5669 shmat03
> This one looks like being dropped from the CVE list purposely,
> according to:
> commit 2588dafd4651706ed7ae34ae3b744b0ee8cd6384
> Author: Cyril Hrubis <chrubis@suse.cz>
> Date: Wed Aug 14 14:13:28 2019 +0200
> syscalls/shmat03: Remove it from runtest/cve
> The original POC[1] and CVE-2017-5669 are not tested by this test
> anymore as it turned out that the CVE was bogus. See:
> https://marc.info/?l=linux-mm&m=152510978123755&w=2
> And the test became regression test for:
> commit 8f89c007b6dec16a1793cb88de88fcc02117bbbc
> Author: Davidlohr Bueso <dave@stgolabs.net>
> Date: Fri May 25 14:47:30 2018 -0700
> ipc/shm: fix shmat() nil address after round-down when remapping
> Hence we will keep the test but remove it from the CVE runtest file and
Good catch, Li. I'm for merging this without "cve-2017-5669 shmat03" line.
With this change:
Reviewed-by: Petr Vorel <pvorel@suse.cz>
> adjust
> the top level comment in the test code.
Do you plan to do this?
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-06-20 21:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 8:03 [LTP] [PATCH v1 1/1] runtest/cve: Add some existing CVE tests to runtest file Souta Kawahara
2023-06-20 8:34 ` Li Wang
2023-06-20 21:08 ` Petr Vorel [this message]
2023-06-21 0:19 ` 河原颯太
2023-06-21 0:20 ` [LTP] [PATCH v2 " Souta Kawahara
2023-06-21 2:37 ` Li Wang
2023-06-21 9:07 ` Martin Doucha
2023-06-21 11:52 ` Li Wang
2023-06-21 12:41 ` Martin Doucha
2023-06-21 12:52 ` Cyril Hrubis
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=20230620210826.GB334441@pevik \
--to=pvorel@suse.cz \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
/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