From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 1EB4FA0542; Tue, 31 May 2022 09:21:01 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C76DF400EF; Tue, 31 May 2022 09:21:00 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 0AD94400D6 for ; Tue, 31 May 2022 09:20:58 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1653981658; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=7Ymv8EJnz517bUbtbPXA2KtZsaLjKs4ddGfmLs+VL1w=; b=fhbRL2yqUSppZBhnRYgTqIx8e5lNfPyshHM1givxmLBLLNjiZcLFcrUSeBa1FeUuQUgsH/ kEP+g9LGwIni5gSwLiOO1gfe9rt65xsRKE5rdt4qnlzfkHqPDw53Yrw3+RT22oJiKvcEk0 gxYizLDT/V9Kar1Q6oBnPtIg1/xmF2Q= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-351-WZZfCfuOMvWtd6j2Za22nQ-1; Tue, 31 May 2022 03:20:57 -0400 X-MC-Unique: WZZfCfuOMvWtd6j2Za22nQ-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id F07F01C01B4B for ; Tue, 31 May 2022 07:20:56 +0000 (UTC) Received: from [10.39.208.26] (unknown [10.39.208.26]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A0F6710725 for ; Tue, 31 May 2022 07:20:56 +0000 (UTC) Message-ID: <689230e8-1b47-57b5-dc80-0e4a898adedf@redhat.com> Date: Tue, 31 May 2022 09:20:55 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 From: Maxime Coquelin Subject: Minutes of Technical Board Meeting, 2022-May-18 To: "dev@dpdk.org" X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=maxime.coquelin@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Members Attending --------------------------- -Aaron -Bruce -Honnappa -Konstantin -Kevin -Maxime (chair) -Olivier -Stephen -Thomas NOTE: The technical board meetings are on every second Wednesday at https://meet.jit.si/DPDK at 3 pm UTC. Meetings are public, and DPDK community members are welcome to attend. NOTE: Next meeting will be on Wednesday 2021-June-1 @3pm UTC, and will be chaired by Olivier. 1) DTS into DPDK repo progress - DTS patches will require some quality exception to get into main repository - Patches are being prepared, they will be sent soon 2) CI testing with packet fuzzing - Thomas suggests packet fuzzing tools would be useful to find issues in drivers - The tool could be run on all interfaces to catch use-after-free and other kind of issues - One possibility could be to use Scapy or other packet generators to testpmd. Some concerns that Scapy would be too slow - Fuzzing tool should not be used for patch gating - Call for ideas for packet fuzzing tools 3) HackerOne bug bounty program - Nathan updated that discussions about DPDK enrollment into HackerOne program won't be pursued - Suggestion about having a hackathon during the DPDK UserSpace event 4) Techwriter hiring update - Nathan received 12 applications, he will wait for one more week to gather more applicants - A first filter will be based on applicants' published work 5) Security process feedback - Kevin sent a mail requesting feedback on current process from people involved in previous vulnerabilities handling - No feedback received for now 6) SPDK vulnerabilities pre-release mailing list membership - The techboard approved SPDK membership with 8 votes for - Stephen suggests to make the vulnerabilities pre-release mailing list more visible on dpdk.org's security pages 7) DPDK UserSpace event update - Conference budget has been approved by the Governing Board - The boat excursion has not been approved. Cocktail/dinner event will need to be approved separately