LTP release
Hi!
It's about a time we should start preparing for another release.
As usuall let's start with pointing out patches that should be part of it, then we will proceed with freezing the repo and round of pre-release testing, etc.
Signature · 2 lines
Cyril Hrubis [email protected]
Hi Alexey,
Quoted 5 lines
It's about a time we should start preparing for another release.
As usuall let's start with pointing out patches that should be part of it, then we will proceed with freezing the repo and round of pre-release testing, etc.
do you consider v9 of "Simplify network setup + fix some multicast network stress tests"
[1]
patch stable enough to be merged?
I've removed everything controversial (to be solved later), but you might have found some other issue.
Kind regards,
Petr
[1] http://lists.linux.it/pipermail/ltp/2017-August/005403.html
Quoted 6 lines · Cyril Hrubis
Hi!
It's about a time we should start preparing for another release.As usuall let's start with pointing out patches that should be part of it, then we will proceed with freezing the repo and round of pre-release testing, etc.
Following pending review/commit right now from me
1. [LTP][RESEND][PATCH v2] android: pty01: Fix pty01 test for Android
2. [LTP][PATCH v4] input/input06: Fix auto-repeat key test
3. [LTP][PATCH v2] android: madvise08: fix for android devices
- ssp
Hi Cyril,
These two patches for ksm are very worth to LTP.
http://lists.linux.it/pipermail/ltp/2017-August/005412.html
Quoted 13 lines · Cyril Hrubis
Hi!
It's about a time we should start preparing for another release.As usuall let's start with pointing out patches that should be part of it, then we will proceed with freezing the repo and round of pre-release testing, etc.
--
Cyril Hrubis
[email protected]--
Mailing list info: https://lists.linux.it/listinfo/ltp
Signature · 2 lines
Li Wang [email protected]
Hello,
Quoted 10 lines · Cyril Hrubis
Hi!
It's about a time we should start preparing for another release.As usuall let's start with pointing out patches that should be part of it, then we will proceed with freezing the repo and round of pre-release testing, etc.
Signature · 2 lines
Cyril Hrubis [email protected]
As you might expect, I am very keen to get the long lived thread support for fuzzy sync into this release:
tst_atomic: Add load, store and use __atomic builtins
tst_atomic: Add atomic store and load tests
fzsync: Add long running thread support and deviation stats
fzsync: Add functionality test for library Convert cve-2016-7117 test to use long running threads Convert cve-2014-0196 to use long running threads Convert cve-2017-2671 to use long running threads
Also the following patches would be nice:
lib: Add personality fallback and SAFE macro
CVE-2012-0957: Use SAFE_PERSONALITY
Test for CVE-2016-10044 mark AIO pseudo-fs noexec
thp01: Find largest arguments size
Add test for CVE-2017-7308 on a raw socket's ring buffer
madvise07: Increase probability of testing a supported page type
Signature · 2 lines
Thank you, Richard.
Hi!
Quoted 17 lines
As you might expect, I am very keen to get the long lived thread support for fuzzy sync into this release:
tst_atomic: Add load, store and use__atomicbuiltins
tst_atomic: Add atomic store and load tests
fzsync: Add long running thread support and deviation stats
fzsync: Add functionality test for library Convert cve-2016-7117 test to use long running threads Convert cve-2014-0196 to use long running threads Convert cve-2017-2671 to use long running threadsAlso the following patches would be nice:
lib: Add personality fallback and SAFE macro
CVE-2012-0957: UseSAFE_PERSONALITY
Test for CVE-2016-10044 mark AIO pseudo-fs noexec
Quoted 5 lines
thp01: Find largest arguments size
Add test for CVE-2017-7308 on a raw socket's ring buffer
madvise07: Increase probability of testing a supported page type
Ack, I will look into these.
Signature · 2 lines
Cyril Hrubis [email protected]
----- Original Message -----
Quoted 6 lines
Hi!
It's about a time we should start preparing for another release.As usuall let's start with pointing out patches that should be part of it, then we will proceed with freezing the repo and round of pre-release testing, etc.
I started running tests (syscalls, misc, commands, etc.) across RHELs:
6.2-6.10(i386,x86_64,ppc64,s390x) and 7.0-7.4(x86_64, ppc64, ppc64le, s390x).
Other than couple small issues that have been fixed, and known kernel bugs, it's looking good.
I'm planning on repeating the tests after the freeze.
Regards,
Jan
Hi!
Quoted 11 lines
Quoted 5 lines
It's about a time we should start preparing for another release.
As usuall let's start with pointing out patches that should be part of it, then we will proceed with freezing the repo and round of pre-release testing, etc.
I started running tests (syscalls, misc, commands, etc.) across RHELs:
6.2-6.10(i386,x86_64,ppc64,s390x) and 7.0-7.4(x86_64, ppc64, ppc64le, s390x).Other than couple small issues that have been fixed, and known kernel bugs, it's looking good.
It's looking good on my side as well.
I still want to fix the utimensat_tests.sh before the release that fails on stable kernels that backported the fix.
Apart from that I would consider tmpfs for EROFS patch, since that one may be a good speed up. And possibly the synchronization library for CVE tests, if Richard manages to send updated patchset.
And that should ideally be all, or have I missed something?
Signature · 2 lines
Cyril Hrubis [email protected]