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=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no 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 0006EC432C0 for ; Mon, 18 Nov 2019 09:51:55 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C19C52075C for ; Mon, 18 Nov 2019 09:51:55 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="XMp6PJLC" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726905AbfKRJvy (ORCPT ); Mon, 18 Nov 2019 04:51:54 -0500 Received: from us-smtp-delivery-1.mimecast.com ([205.139.110.120]:55356 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726562AbfKRJvx (ORCPT ); Mon, 18 Nov 2019 04:51:53 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1574070712; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=RnkPtrtkzLDiLhVBi6u0mh9f/xmCiH2CgLmKPX7+Qck=; b=XMp6PJLCy1mSrUH4p9zEuUUREwme/OjBAZkta4K8wFj0lmgmeubOJC4n+NmZcy5Qb7Sf8/ OwTPASCIBUZir/BkEBL9N8/3FBDyhqEARIOFXCsct1vr1fKF/EXHEpskhWap+PtvNkRBXz dn5Q6vsBNgK1FEmFffWCNhs9ZFO5K/c= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-136-tlNJaAxFMeuMcg0GwrRpbQ-1; Mon, 18 Nov 2019 04:51:49 -0500 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id E5120107ACCC; Mon, 18 Nov 2019 09:51:47 +0000 (UTC) Received: from localhost (ovpn-204-195.brq.redhat.com [10.40.204.195]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A7BEC2934D; Mon, 18 Nov 2019 09:51:46 +0000 (UTC) Date: Mon, 18 Nov 2019 10:51:45 +0100 From: Jiri Benc To: Willem de Bruijn Cc: Daniel Borkmann , bpf , Network Development , Willem de Bruijn Subject: Re: [PATCH bpf] selftests: bpf: fix test_tc_tunnel hanging Message-ID: <20191118105145.3e576745@redhat.com> In-Reply-To: References: <60919291657a9ee89c708d8aababc28ebe1420be.1573821780.git.jbenc@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-MC-Unique: tlNJaAxFMeuMcg0GwrRpbQ-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Sender: bpf-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org On Fri, 15 Nov 2019 17:05:42 -0500, Willem de Bruijn wrote: > Ah, a typo. This is the SHA1 in my tree, note the aa9d --> aa99d >=20 > $ git fetch davem-net-next > $ git log -1 --oneline -- tools/testing/selftests/bpf/test_tc_tunnel.sh > f6ad6accaa99d selftests/bpf: expand test_tc_tunnel with SIT encap Indeed, it should have been: Fixes: f6ad6accaa99 ("selftests/bpf: expand test_tc_tunnel with SIT encap") Not sure how that happened, I'm sorry for that. Thanks for catching it. Should I resend with the fixed commit message? Sorry again, Jiri