From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.7 required=3.0 tests=BAYES_00,FROM_LOCAL_HEX, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7213EC433E0 for ; Thu, 4 Feb 2021 09:50:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2FAD564F59 for ; Thu, 4 Feb 2021 09:50:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235292AbhBDJuE (ORCPT ); Thu, 4 Feb 2021 04:50:04 -0500 Received: from mail-io1-f70.google.com ([209.85.166.70]:48779 "EHLO mail-io1-f70.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233597AbhBDJuC (ORCPT ); Thu, 4 Feb 2021 04:50:02 -0500 Received: by mail-io1-f70.google.com with SMTP id v25so2335733ioj.15 for ; Thu, 04 Feb 2021 01:49:46 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=wezkJ1F8agCdcNjDqul8IKeKPpbHJSliiOEYiB+1HcI=; b=XTSyiPTxJjwlfr1XbpT3918tasTrGj9e+ZjvO6n5NOGl7o4UBSYmVJ+Eo+fG4n+Ba7 w0s0to6S/dUIyLVbzdzFznJStmBk1/GExqsXoPnyRy2x58jtsYrm1zic+wl65SQnSFzI pYw+MMj6dCrOWRAq/09+agk/e2+KD4r09St4pzTdNLbsTjDcehcGOdgAqQnpU7pJr+bS ARF7+GsepTPNvqIAPyLMqN6DfD31sCshToefpM/vvdsXqwKOpPyYeG5zMf4WwXuz8clY BYQE+5SQ0kkb//t6QEjrcRSZsUnUSmaoziJ/ABcOnxMoXgSYqE/LNzCIJC1p4RW8WRvX g5Ww== X-Gm-Message-State: AOAM533vtyVUoFGIY1DSxIs32YYVOT9AL4myiFlVs8dCVbnNz0nQwz2R eH95MEMPHFg9CGZIJp1i3KLiw7Yfu4oVbY6UwKZhdrMPMPp8 X-Google-Smtp-Source: ABdhPJxn89wvVSmBzs6jHR80e7eLfWyCrqqkfpQY9GIw7QqyDMM0XTCeEtaxzkQIEKZ9HDpKwbO80s3x/PkycV1C71SYU8DODBYz MIME-Version: 1.0 X-Received: by 2002:a05:6638:6b2:: with SMTP id d18mr4855450jad.26.1612432161207; Thu, 04 Feb 2021 01:49:21 -0800 (PST) Date: Thu, 04 Feb 2021 01:49:21 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000003178bf05ba7f9e84@google.com> Subject: upstream test error: BUG: got no fallback coverage: From: syzbot To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, syzbot found the following issue on: HEAD commit: 6642d600 Merge tag '5.11-rc5-smb3' of git://git.samba.org/.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=14de59e8d00000 kernel config: https://syzkaller.appspot.com/x/.config?x=f75d66d6d359ef2f dashboard link: https://syzkaller.appspot.com/bug?extid=e6ca682acbbf21043787 userspace arch: arm64 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+e6ca682acbbf21043787@syzkaller.appspotmail.com 1970/01/01 00:02:05 connecting to host at 10.0.2.10:40353 1970/01/01 00:02:05 checking machine... 1970/01/01 00:02:05 checking revisions... ps_root_recvmsgcb: failed to send message to pid 4476: Connection refused 1970/01/01 00:02:05 testing simple program... 1970/01/01 00:02:08 BUG: got no fallback coverage: loop exited with status 11 ps_root_recvmsgcb: failed to send message to pid 4508: Connection refused ps_root_recvmsgcb: failed to send message to pid 4544: Connection refused ps_root_recvmsgcb: failed to send message to pid 4543: Connection refused ps_bpf_start_bpf: bpf_open: Invalid argument ps_root_recvmsg: Invalid argument ps_bpf_start_bpf: bpf_open: Invalid argument ps_root_recvmsg: Invalid argument ps_bpf_start_bpf: bpf_open: Invalid argument ps_root_recvmsg: Invalid argument --- This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller@googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot.