From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: Wake Liu <wakel@google.com>,
Kodanda Rami Reddy V <quic_kreddyv@quicinc.com>,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] Ignore cve-2022-2590_64bit CVE for Kernel versions below 5.16+
Date: Fri, 21 Nov 2025 17:15:45 +0100 [thread overview]
Message-ID: <20251121161545.GA14501@pevik> (raw)
In-Reply-To: <aRy0-9KIPlRBvnNk@yuki.lan>
Hi Kodanda, all,
> Hi!
> > CVE 2022-2590_64bit is applicable only for kernel versions 5.16 onwards.
The fix 5535be309971 (actually FOLL_COW removal) was merged into v6.0-rc3.
Probably because this is feature change it was not merged into 5.15 stable and
the older trees. If we want to mask older kernels IMHO it should be on kernels
older than 6.0.
But we don't want to hide bugs, right?
> Why? What happens if you run the test on an older kernel? This
> information should be written here.
> > Add kernel version check to skip/Ignore the test case.
> > Test Module: vts_ltp_test_arm_64
> > Test Case: cve.cve-2022-2590_64bit#cve.cve-2022-2590_64bit
very nit: the subject should not have "_64bit".
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-11-21 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 3:40 [LTP] [PATCH] Ignore cve-2022-2590_64bit CVE for Kernel versions below 5.16+ Wake Liu via ltp
2025-11-18 18:03 ` Cyril Hrubis
2025-11-21 16:15 ` Petr Vorel [this message]
2025-11-28 6:48 ` [LTP] [PATCH v2] dirtyc0w_shmem: Add minimum kernel version 6.0 check Madhu Ananthula via ltp
2025-12-04 7:22 ` Madhu Ananthula (Temp) via ltp
2025-12-08 9:38 ` Madhu Ananthula (Temp) via ltp
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=20251121161545.GA14501@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=quic_kreddyv@quicinc.com \
--cc=wakel@google.com \
/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