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=-3.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_PASS,USER_AGENT_GIT 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 83826C169C4 for ; Wed, 30 Jan 2019 00:38:30 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 46CAD2087F for ; Wed, 30 Jan 2019 00:38:30 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=fb.com header.i=@fb.com header.b="EItswIGb" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729814AbfA3Ai3 (ORCPT ); Tue, 29 Jan 2019 19:38:29 -0500 Received: from mx0b-00082601.pphosted.com ([67.231.153.30]:58022 "EHLO mx0b-00082601.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729704AbfA3AiX (ORCPT ); Tue, 29 Jan 2019 19:38:23 -0500 Received: from pps.filterd (m0109331.ppops.net [127.0.0.1]) by mx0a-00082601.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x0U0bvw2003612 for ; Tue, 29 Jan 2019 16:38:22 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : cc : subject : date : message-id : mime-version : content-type; s=facebook; bh=0HEgiG1tequzPjdvWysl0QWNj1yfJEITtbwhbxaCJhk=; b=EItswIGbBfuUr+lyhAJ/f+75Y+BIc1Xb5sTDEfzPgVgVIYMLr4FrwhdnlOoCJZUkytd4 tJubnSP5Inn1sFOD71zZ0LcLMJy6ZudW2U/cXGYZqWG2WkAyX8tc+vVJVFT4r/BlD8Yi DAqKHl3Wfh/bXlhuShELDt3KHM+8oqCOmS8= Received: from mail.thefacebook.com ([199.201.64.23]) by mx0a-00082601.pphosted.com with ESMTP id 2qb0xug3af-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for ; Tue, 29 Jan 2019 16:38:22 -0800 Received: from mx-out.facebook.com (2620:10d:c081:10::13) by mail.thefacebook.com (2620:10d:c081:35::127) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA) id 15.1.1531.3; Tue, 29 Jan 2019 16:38:21 -0800 Received: by devbig003.ftw2.facebook.com (Postfix, from userid 128203) id 2C82B37023B4; Tue, 29 Jan 2019 16:38:16 -0800 (PST) Smtp-Origin-Hostprefix: devbig From: Yonghong Song Smtp-Origin-Hostname: devbig003.ftw2.facebook.com To: CC: Alexei Starovoitov , Daniel Borkmann , , Yonghong Song Smtp-Origin-Cluster: ftw2c04 Subject: [PATCH bpf 0/2] bpf: btf: allow typedef func_proto Date: Tue, 29 Jan 2019 16:38:16 -0800 Message-ID: <20190130003816.1043826-1-yhs@fb.com> X-Mailer: git-send-email 2.17.1 X-FB-Internal: Safe MIME-Version: 1.0 Content-Type: text/plain X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-01-29_19:,, signatures=0 X-Proofpoint-Spam-Reason: safe X-FB-Internal: Safe Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org The current btf implementation disallows the typedef of a func_proto type. This actually is allowed per C standard. This patch fixed btf verification to permit such types. Patch #1 fixed the kernel side and Patch #2 fixed the tools test_btf test. Yonghong Song (2): bpf: btf: allow typedef func_proto tools/bpf: fix test_btf for typedef func_proto case kernel/bpf/btf.c | 3 ++- tools/testing/selftests/bpf/test_btf.c | 9 +++------ 2 files changed, 5 insertions(+), 7 deletions(-) -- 2.17.1