On 3 February 2018 at 05:18, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Fri, Feb 02, 2018 at 10:35:19PM -0600, Dan Rue wrote:
On Fri, Feb 02, 2018 at 05:58:18PM +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.15.1 release. There are 55 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Sun Feb 4 14:07:50 UTC 2018. Anything received after that time might be too late.
The whole patch series can be found in one patch at: kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.15.1-rc1.gz or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.15.y and the diffstat can be found below.
Results from Linaro’s test farm.
No regressions since 4.15 release, but you'll notice high failure counts in kselftest. These are because it was the first RC and I ran the tests multiple times - first without a skipfile, and then again with a partial skipfile. All of the failures look like known issues that we also saw on 4.15 release.
Why does kselftest need a "skip list"? Shouldn't all of the tests that ship in the kernel tree, pass on that release? Is anyone looking into the failures? That seems like a pretty obvious thing :(
They should and it would be great to see that. Unfortunately this isn't he case. Some examples (from 4.15): test_kmod.sh - path to the module is wrong https://lkml.org/lkml/2017/11/6/654
sync - missing cflags in makefile https://patchwork.kernel.org/patch/10166499/
seccomp_bpf - open(2) is a legacy syscall, replaced with openat(2) since 2.6.16 https://lkml.org/lkml/2018/1/9/1141
reuseport_bpf: this test doesn't give consistent results. It usually fails when ran from run_kselftests.sh script. Passes when run standalone on 1st attempt and fails again on 2nd attempt.
There is also a group of tests (BPF) that are not correctly built in our openembedded build. The OE recipe needs to be fixed to make sure all .o files are where they are expected to be. There are more failed tests, but I don't have a good explanation what is going on.
And was anyone testing the -rc releases to catch this before 4.15 came out? If not, why not? I thought you all were testing rc releases now...
These are usually old problems and they are also included in the skiplist for mainline. We're trying to report any regressions in mainline tests, but this work has slightly lower priority than LTS :(
milosz
Anyway, thanks for the reports.
thanks,
greg k-h _______________________________________________ Lkft-triage mailing list Lkft-triage@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lkft-triage