From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 1E645A0096 for ; Wed, 5 Jun 2019 18:33:36 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id EA2D91BBF4; Wed, 5 Jun 2019 18:33:35 +0200 (CEST) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by dpdk.org (Postfix) with ESMTP id 8E81A1BBA1; Wed, 5 Jun 2019 18:33:34 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id BED2E55F; Wed, 5 Jun 2019 12:33:30 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 05 Jun 2019 12:33:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=n83ku5QregbadIV6g9/RqBfKGIvLAJKfwZkAc1vjG2g=; b=ZFUGOU032o0d nNdJfluVOWYkA+fWF6tqA09IvFh82YFJ+8rgxJkcjTsGq09m++cYVfUlyw/Wcm8i 60Ld+haoeVx3muTT3HBXcSO5ACn19ug/aVUOKk9rsK6EXUDVsNAhcWWghLinTYpB tCNJycUwaj7mjLrenyHsWKol2u9PMnA= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=n83ku5QregbadIV6g9/RqBfKGIvLAJKfwZkAc1vjG 2g=; b=cq+RWkcAwvFdAjQ4Q0DAYzPK9gumKWvSizto2Z4lQisvfGzuzNHfAyU/e VRPZrftsQT0F7eGuNSRkz+I89HD8qNy6rVTwX95vUqDm+mI9bls302dYpgRCb3Aw 4EltfLEFgixVnApb9BDsNF85Wf/tEu/t3EpIdjOnGJD69EWz4XS1MGg0GdlLf3fM 9JcLR7zS9nD6JqEJ2AiVWgY+/TvxOi8Gh/58x85UmKNRFYYILzKU+iSuJxPBnkDk oZKe3mic6LgBTn1pWbIGhYUgUKxFY82nsndhHVOouSQO9pZWBo+xoqI/Yk38Gi1z zUOZ78W4reKhv5jmDqQzRhI0aYOwg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudegvddguddthecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ffohhmrghinhepughpughkrdhorhhgpdhlfihnrdhnvghtnecukfhppeejjedrudefgedr vddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjh grlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 44A9F80068; Wed, 5 Jun 2019 12:33:29 -0400 (EDT) From: Thomas Monjalon To: Konstantin Ananyev Cc: dev@dpdk.org, stable@dpdk.org Date: Wed, 05 Jun 2019 18:33:28 +0200 Message-ID: <1853797.H4zF8rg7Bj@xps> In-Reply-To: <20190517140942.20724-1-konstantin.ananyev@intel.com> References: <20190517140942.20724-1-konstantin.ananyev@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] bpf: fix pseudo calls for BPF programs loaded from ELF X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 17/05/2019 16:09, Konstantin Ananyev: > clang 6.0 and onwards, for the external function call generates > BPF_PSEUDO_CALL instruction: > call pseudo +-off -> call another bpf function. > More details about that change: https://lwn.net/Articles/741773/ > DPDK BPF implementation right now doesn't support multiple BPF > functions per module. > To overcome that problem, and preserve existing functionality > (ability to call allowed by user external functions), > bpf_elf_load() clears EBPF_PSEUDO_CALL value. > For details how to reproduce the issue: > https://bugs.dpdk.org/show_bug.cgi?id=259 > > Fixes: 5dba93ae5f2d ("bpf: add ability to load eBPF program from ELF object file") > Cc: stable@dpdk.org > > Signed-off-by: Konstantin Ananyev Applied, thanks