On Oct 13, 2017, at 5:31 AM, Greg KH gregkh@google.com wrote:
On Mon, Oct 09, 2017 at 09:44:36AM +0000, Linaro QA wrote:
Summary
kernel: 4.9.54 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.9.y git commit: f37eb7b586f1dd24a86c50278c65322fc6787722 git describe: v4.9.54 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.54
Hm, I don't seem to have a test result here for 4.9.55-rc1, so I'm hijacking this thread to ask what happened to the tests there?
Was posted to linux-stable on Oct 11.
Turns out that 4.9.55-rc1 did not work at all for networking, yet no tests seem to have caught it. Are we not testing something with a network here? You said you were using NFS, how did that work?
Anything we can do to add to the tests to verify that basic dhcp works? We should learn from our mistakes…
You’ve probably heard me and/or others lament about coverage. I see that is an issue that *we* the linux-stable community need to hash out.
Frankly across the entire android community with all the companies that do some amount of kernel effort, we all should be looking at LTS and thinking about how to test it better. LKFT is really only a start. Failures like you saw this time around, illustrate we need to go further. That’s my session idea over the next year at various open source conferences.
Putting my Android hat on, it does bug me that we’re not merging and testing the rc LTS patches as part of the rc cycle. It’s work I know but has to be done at some point. Why wait? It sounds like you might be doing this on Google’s infra already?
Amit Pundir has a public mainline tree that blends the out of tree android common patches with mainline as the rcs roll by. That sees some amount of testing. We haven’t put it into LKFT but we sure could.
Heck, the simple build/boot tests that Google runs instantly found this issue when I tried to merge 4.9.55 into the android-common trees, maybe I should just rely on thost tests from now on?
You’d think that even the linux distro community (if they were watching RCs) should have picked it up as well.
Dan’s comment about dhclient needing to be involved is spot on tho.
Because of this, I had to release 4.9.56 a few hours later fixing the issue. This doesn't make me feel like I can trust this testing effort at all just yet, given the track record it has shown this past week. We have had two known-bad kernel releases and none of this testing caught it at all (both were caught by community members...) :(
Given that dhclient were required for those one of the uncaught errors, and KASAN the other, this illustrates the slippery slope that can quickly become distro testing and trying to do infinite combinations.
Gentoo finds a bug, debian doesn’t therefore Debian can’t be trusted. We’ve both lived in that world Greg, and I hope you appreciate the logic when I observe what you are saying is not a fair comment.
I hope you agree, we in the linux stable community have a coverage problem and we need to collectively get more eyeballs and own up to expanding what we’re doing.
In the android world there ought to be a fairly good swath of kernel engineers that should deeply care about 6 year (or whatever) LTS and pitch in. It won’t happen overnight.
Back to booting the kernels on my laptop and running 'make allmodconfig', that's found more errors so far than anything else...
greg k-h _______________________________________________ Lts-dev mailing list Lts-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lts-dev