Received: by 2002:a05:6358:489b:b0:bb:da1:e618 with SMTP id x27csp2209392rwn; Fri, 9 Sep 2022 10:02:40 -0700 (PDT) X-Google-Smtp-Source: AA6agR7mQbYQZ9WhWTTCruZkx1i4zc7NlcRauJIDDkg917KoAhkw0U67pKWRCG9aq01afBD03dhr X-Received: by 2002:aa7:9e52:0:b0:53e:49b2:1c6e with SMTP id z18-20020aa79e52000000b0053e49b21c6emr15357172pfq.70.1662742960160; Fri, 09 Sep 2022 10:02:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1662742960; cv=none; d=google.com; s=arc-20160816; b=cIVtDe6lCnqK1FWPu+G+vZzDkj/S4qgJLsaqO6cGZOJMwx3Bo49JhwABnimaOWcMvi Hdewt+dFG/eUD6+aiKSFqbTDuDMekYn6VjDvf/2DqPvYhZ+D0ZPfPVnHrVHo2OF/se5C S3wkpSFb1xiFLs/CDU9uNL2e/T+29JJyWy2D1HXzpyucy4nv3FZPMh2YXHyY1sVfF2lC vmfwOHyvhBSFJhSPE0z8liVjEKSyrEpWY9kEkW01SXXPHsTe/3kVkAMaVKiyuYNJvGh0 HCDCdTU5K20lI/H8bUh59E083BmA3S4/oX4mH9AF68ZW6FPEujlZc7ZPjaP5Ipjo2EU+ pMQA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=TgO3N0qP8iuZUQ578O33EC3J9Pns4trql2X/6qLcYJc=; b=N05wNln58e7MupvoOaHeo4HGygq54AyiOABZuTFL8EosjIegTZjrGTV7vDA9v6KStw 4/JV3EvEZ9g+XAaH61Zva+z4vpGOiF7VWeKrnAC51u6i9nnZ8jR/VfCRSyi3YZ6ZqaCc C5rXW0mPBVtqWpnFLkNlqpM+qTA04k6HV9gTHAACiz3AFJ2wHtNW/cFwUnfZTjH186nw NcNglsaD6tR+7pamhgLxxDiRtjFqxeaOmNa8ygVE7A5N/Q58VsnpWx0+fCVzK02kphfr amkuzspqj9SwU2m9be8Fmq7j5GnLkC/36ku5PapAl5Mk+HvGu5wkL+uB+PN+891OONkS HORw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=dIoogj0v; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id lb10-20020a17090b4a4a00b00200b96d234csi1054316pjb.49.2022.09.09.10.02.24; Fri, 09 Sep 2022 10:02:40 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=dIoogj0v; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231223AbiIIQxI (ORCPT + 99 others); Fri, 9 Sep 2022 12:53:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49560 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229774AbiIIQxE (ORCPT ); Fri, 9 Sep 2022 12:53:04 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4A19A7E301 for ; Fri, 9 Sep 2022 09:53:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1662742382; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=TgO3N0qP8iuZUQ578O33EC3J9Pns4trql2X/6qLcYJc=; b=dIoogj0vSoyUj7jQ9uo7g1OV7E1nSAo2rAw01NTFI+Vl1paKT0qLinYsMBQsbweJ230GrI hJ38elJaUscgHGjxgva64w1hTj1Kw3pI+xD/xdBH+Y8zj6ZXnkkvtSCmBeGL8SojpnuI5a mkl/5OegyFQcxgpLjZrU3xI3wVNJzoM= Received: from mail-pf1-f200.google.com (mail-pf1-f200.google.com [209.85.210.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-630-bJkBj7Q3NZKkyENvSaZ14w-1; Fri, 09 Sep 2022 12:53:01 -0400 X-MC-Unique: bJkBj7Q3NZKkyENvSaZ14w-1 Received: by mail-pf1-f200.google.com with SMTP id w22-20020a627b16000000b0054109970446so491326pfc.8 for ; Fri, 09 Sep 2022 09:53:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=TgO3N0qP8iuZUQ578O33EC3J9Pns4trql2X/6qLcYJc=; b=vYB9zd9rVFJ2Xh7Ut0/HEwR7RYfJcszQ1PUMLU6Df5WferWlrxLZIEZ9MrTSXmzaie 2Epcu1gkihQmWg1ehIdwbLPp9Jbrajo2pFlfGJRrwd87IyDWkHkCqh9uORx7sJFRbejU dGOgKBcm7fx6+yU7Wg0wG1jFtyfuSk/UpqIHm/UGWt7Zx4knqR4ehuzWFWFdvfdt2/7v 3X6vehel7YEyeZYfrZATsgPUv4li4PiIiqMgIMnsGJdqiy3Da7Bpv9WZEeSEA+o0O9w9 7Qtu6qmHGyWRDSDY0sdkPv8PK1PizSuzaHMJqMYE0/R0Ut56uT/M0WPaSyopeI3q7OpK +WPg== X-Gm-Message-State: ACgBeo11WKomDaZzfOqu8Xgb37KRHioYhhHxKKeRFtzKrSpFJCG5dRQZ CFV4KxzKFOVOMyY9BwJDnQEG5vqHnzuwUpuHmLzAogsAOoVygB1EGHJ1cjR9oqA0DmfqNSyu3lS fMSQFxz5lKV5ZKlH4QrOz0qRQ2g4R6iAgLY7u+rIA X-Received: by 2002:a63:d10b:0:b0:41d:bd7d:7759 with SMTP id k11-20020a63d10b000000b0041dbd7d7759mr12939025pgg.196.1662742379913; Fri, 09 Sep 2022 09:52:59 -0700 (PDT) X-Received: by 2002:a63:d10b:0:b0:41d:bd7d:7759 with SMTP id k11-20020a63d10b000000b0041dbd7d7759mr12939005pgg.196.1662742379643; Fri, 09 Sep 2022 09:52:59 -0700 (PDT) MIME-Version: 1.0 References: <000000000000e506e905e836d9e7@google.com> In-Reply-To: From: Benjamin Tissoires Date: Fri, 9 Sep 2022 18:52:48 +0200 Message-ID: Subject: Re: [syzbot] WARNING in bpf_verifier_vlog To: sdf@google.com Cc: Andrii Nakryiko , Alexei Starovoitov , bpf , Daniel Borkmann , davem@davemloft.net, haoluo@google.com, hawk@kernel.org, John Fastabend , jolsa@kernel.org, KP Singh , kuba@kernel.org, lkml , llvm@lists.linux.dev, martin.lau@linux.dev, nathan@kernel.org, Nick Desaulniers , Networking , Song Liu , syzkaller-bugs@googlegroups.com, Tom Rix , Yonghong Song Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Sep 9, 2022 at 6:37 PM wrote: > > On 09/08, syzbot wrote: > > Hello, > > > syzbot found the following issue on: > > > HEAD commit: 7e18e42e4b28 Linux 6.0-rc4 > > git tree: upstream > > console+strace: https://syzkaller.appspot.com/x/log.txt?x=1551da55080000 > > kernel config: https://syzkaller.appspot.com/x/.config?x=f4d613baa509128c > > dashboard link: > > https://syzkaller.appspot.com/bug?extid=8b2a08dfbd25fd933d75 > > compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU > > Binutils for Debian) 2.35.2 > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1798cab7080000 > > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16ccbdc5080000 > > > Downloadable assets: > > disk image: > > https://storage.googleapis.com/syzbot-assets/da260c675b46/disk-7e18e42e.raw.xz > > vmlinux: > > https://storage.googleapis.com/syzbot-assets/58f7bbbaa6ff/vmlinux-7e18e42e.xz > > > IMPORTANT: if you fix the issue, please add the following tag to the > > commit: > > Reported-by: syzbot+8b2a08dfbd25fd933d75@syzkaller.appspotmail.com > > > ------------[ cut here ]------------ > > verifier log line truncated - local buffer too short > > WARNING: CPU: 1 PID: 3604 at kernel/bpf/verifier.c:300 > > bpf_verifier_vlog+0x267/0x3c0 kernel/bpf/verifier.c:300 > > Modules linked in: > > CPU: 1 PID: 3604 Comm: syz-executor146 Not tainted 6.0.0-rc4-syzkaller #0 > > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS > > Google 08/26/2022 > > RIP: 0010:bpf_verifier_vlog+0x267/0x3c0 kernel/bpf/verifier.c:300 > > Code: f5 95 3d 0c 31 ff 89 ee e8 06 07 f0 ff 40 84 ed 75 1a e8 7c 0a f0 > > ff 48 c7 c7 c0 e7 f3 89 c6 05 d4 95 3d 0c 01 e8 fb 4c ae 07 <0f> 0b e8 62 > > 0a f0 ff 48 89 da 48 b8 00 00 00 00 00 fc ff df 48 c1 > > RSP: 0018:ffffc900039bf8a0 EFLAGS: 00010282 > > RAX: 0000000000000000 RBX: ffff888017a19210 RCX: 0000000000000000 > > RDX: ffff888021fb1d80 RSI: ffffffff8161f408 RDI: fffff52000737f06 > > RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000 > > R10: 0000000080000000 R11: 0000000000000000 R12: ffffffff89f5aba0 > > R13: 00000000000003ff R14: ffff888017a19214 R15: ffff888012705800 > > FS: 0000555555cba300(0000) GS:ffff8880b9b00000(0000) > > knlGS:0000000000000000 > > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > > CR2: 0000000020100000 CR3: 000000001bf9e000 CR4: 0000000000350ee0 > > Call Trace: > > > > __btf_verifier_log+0xbb/0xf0 kernel/bpf/btf.c:1375 > > __btf_verifier_log_type+0x451/0x8f0 kernel/bpf/btf.c:1413 > > btf_func_proto_check_meta+0x117/0x160 kernel/bpf/btf.c:3905 > > btf_check_meta kernel/bpf/btf.c:4588 [inline] > > btf_check_all_metas+0x3c1/0xa70 kernel/bpf/btf.c:4612 > > btf_parse_type_sec kernel/bpf/btf.c:4748 [inline] > > Benjamin, this seems to be coming from BTF loading. Could this be caused > by some of your recent activity with things like: > > commit f9b348185f4d684cc19e6bd9b87904823d5aa5ed > Author: Benjamin Tissoires > Date: Tue Sep 6 17:13:01 2022 +0200 > > bpf/btf: bump BTF_KFUNC_SET_MAX_CNT > > ? I doubt this commit is the culprit for 2 reasons: - BTF_KFUNC_SET_MAX_CNT just sets the size of an internal memory chunk where we store kfunc definitions. I don't really see how this could be linked to a verifier log being full - this commit has been applied on Sep 7, and the first crash in the dashboard was from Sep 5. So unless the dates are wrong, I don't think this commit creates the crash. Unfortunately, I am really new into the bpf/btf world, and I have no ideas on what could be the cause of that crash. We probably need a bisect, but I'll be out next week at plumbers, so can't really work on that now. Cheers, Benjamin > > I haven't looked too deep, maybe you can give it a shot? There is > reproducer; should be relatively easy to verify. Thx. > > > > btf_parse kernel/bpf/btf.c:5031 [inline] > > btf_new_fd+0x939/0x1e70 kernel/bpf/btf.c:6710 > > bpf_btf_load kernel/bpf/syscall.c:4314 [inline] > > __sys_bpf+0x13bd/0x6130 kernel/bpf/syscall.c:4998 > > __do_sys_bpf kernel/bpf/syscall.c:5057 [inline] > > __se_sys_bpf kernel/bpf/syscall.c:5055 [inline] > > __x64_sys_bpf+0x75/0xb0 kernel/bpf/syscall.c:5055 > > do_syscall_x64 arch/x86/entry/common.c:50 [inline] > > do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 > > entry_SYSCALL_64_after_hwframe+0x63/0xcd > > RIP: 0033:0x7fb092221c29 > > Code: 28 c3 e8 2a 14 00 00 66 2e 0f 1f 84 00 00 00 00 00 48 89 f8 48 89 > > f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 > > ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 > > RSP: 002b:00007fff5b0a6878 EFLAGS: 00000246 ORIG_RAX: 0000000000000141 > > RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fb092221c29 > > RDX: 0000000000000020 RSI: 0000000020000240 RDI: 0000000000000012 > > RBP: 00007fb0921e5dd0 R08: 0000000000000000 R09: 0000000000000000 > > R10: 0000000000000000 R11: 0000000000000246 R12: 00007fb0921e5e60 > > R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 > > > > > > --- > > 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. > > syzbot can test patches for this issue, for details see: > > https://goo.gl/tpsmEJ#testing-patches >