On Tue, Sep 10, 2019 at 09:58:10AM +0100, Greg KH wrote:
On Tue, Sep 10, 2019 at 04:19:56PM +0800, Hangbin Liu wrote:
On Wed, Aug 28, 2019 at 08:36:14AM -0400, CKI Project wrote:
Hello,
We ran automated tests on a patchset that was proposed for merging into this kernel tree. The patches were applied to:
Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git Commit: f7d5b3dc4792 - Linux 5.2.10The results of these automated tests are provided below.
Overall result: FAILED (see details below) Merge: OK Compile: OK Tests: FAILEDAll kernel binaries, config files, and logs are available for download here:
https://artifacts.cki-project.org/pipelines/128519
One or more kernel tests failed:
x86_64: ❌ Networking socket: fuzz
Sorry, maybe the info is a little late, I just found the call traces for this failure.
And this is no longer failing?
I haven't seen this issue later. But you know, this was triggered by a fuzz test, not sure if the bad code still exists.
What is the "fuzz" test?
It's just a socket test that create all kinds of domains/types/protocols and do some {set,get}sockopt for TCP/UDP/SCTP https://github.com/CKI-project/tests-beaker/blob/master/networking/socket/fu...
Xiumei Mu also forwarded me a mail. It looks Sasha has fixed something. But I don't know the details.
----- Forwarded Message -----
From: "Sasha Levin" sashal@kernel.org To: "Greg KH" greg@kroah.com Cc: "Major Hayden" major@mhtx.net, "CKI Project" cki-project@redhat.com, "Linux Stable maillist" stable@vger.kernel.org, "Yi Zhang" yi.zhang@redhat.com, "Xiumei Mu" xmu@redhat.com, "Hangbin Liu" haliu@redhat.com, "Ying Xu" yinxu@redhat.com Sent: Wednesday, August 28, 2019 2:25:36 AM Subject: Re: ❌ FAIL: Test report for kernel 5.2.11-rc1-9f63171.cki (stable)
On Tue, Aug 27, 2019 at 07:05:18PM +0200, Greg KH wrote:
On Tue, Aug 27, 2019 at 09:35:30AM -0500, Major Hayden wrote:
On 8/27/19 7:31 AM, CKI Project wrote:
x86_64: Host 2: ❌ Networking socket: fuzz [9] ❌ Networking sctp-auth: sockopts test [10]
It looks like there was an oops when these tests ran on 5.2.11-rc1 and the last set of patches in stable-queue:
Can you bisect?
I think I've fixed it, let's see what happens next run.
-- Thanks, Sasha