From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <thomas@monjalon.net> Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 986731B44D for <dev@dpdk.org>; Thu, 10 Jan 2019 00:55:58 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id E0FD6233B2; Wed, 9 Jan 2019 18:55:57 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 09 Jan 2019 18:55:57 -0500 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=1gFte0bv0YQDVWEVF5rmeTsQp4XQ0ULgGxuCPCoLS1I=; b=KX9eIZT6BuYf H13WLquRJzxPzuPeWcEO9tKtcYLn2dC7iUBH1m4Rc9J3PePLUeIWwhWUntMVpWHP /XzKN8yuh383LlCXQ/ygvhe4Jqpz6EqZ/cXjn4Z4xigg9H2aiNmk6ZzhqEVNMDY3 uMtAyzJqCNOweO8aa4HQxU97+zZ00ow= 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=fm1; bh=1gFte0bv0YQDVWEVF5rmeTsQp4XQ0ULgGxuCPCoLS 1I=; b=ESCoNO3+GymtEeAVI1yhP0Cy4/eKgVEGP5KIEq9GikrtLYVrCp85hDNsp zICPuXUSN6Gq0ggdiBO4msEyMJ05y9Zs5Z2NwIxKjPb265FCYQUWLHEEAU3s4R8p mXNkbNhh45acmFNQ/61WXqbGGP//hDF3z5dy3bftZbpNF/F8IFb+G4ArhiJe70dc Mlpv1vCcKP+eAIbInodrB380q6Nn6QaidL1ebgtlNRTUc1Vp1UY9PjKDaCuwEN6z En8q8pX2IzETxHQWviQ+hJ5+36LUVrshTKnbGbL0ojXlYhCta2KfSLst5U1hgUe/ 0i/7QTLa168GfBdj50MsAcTaUlKhw== X-ME-Sender: <xms:DYo2XMfZDtgkHx3ahbNHCGy_KweWJR8iMEYOaA848H5T4H_uff22iA> X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrfedvgddugeculddtuddrgedtkedrtddtmd cutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedu X-ME-Proxy: <xmx:DYo2XDeNbrroZtt22B8nHYIx8_xHs6vhfLsbLh1WZchds3RGyt1Y-g> <xmx:DYo2XPMpOW3VOsCgMxkdBN-ITxZSKZQInDMXk7SmWUqZOetRDN3myA> <xmx:DYo2XKIkVHfasdw5TCD8Jvi5bG6oHLtgECxwwnigDbVC9lph3wdEUw> <xmx:DYo2XBZXZaE54PGPaxBrMz7_UYLk_S76KVrcw20-53j0dhDmw-XfJg> Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id B55AFE435E; Wed, 9 Jan 2019 18:55:56 -0500 (EST) From: Thomas Monjalon <thomas@monjalon.net> To: keith.wiles@intel.com Cc: dev@dpdk.org, Daniel Pharos <danielpharos@hotmail.com> Date: Thu, 10 Jan 2019 00:55:55 +0100 Message-ID: <2388397.y9xPINh2BO@xps> In-Reply-To: <DB3PR0402MB3834179FB16B6E4027FFF8A8D38B0@DB3PR0402MB3834.eurprd04.prod.outlook.com> References: <DB3PR0402MB3834179FB16B6E4027FFF8A8D38B0@DB3PR0402MB3834.eurprd04.prod.outlook.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] Seg fault with GRE in pktgen X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Wed, 09 Jan 2019 23:55:58 -0000 Adding Keith Wiles, maintainer of pktgen. 09/01/2019 02:53, Daniel Pharos: > Hi, > > Using pktgen 3.6.1, I'm getting a seg fault when enabling GRE. In app/pktgen.c, on line 556 l3_hdr is set to NULL, and then on line 567 it is send to a function that calls memset on it, triggering the seg fault I'm seeing. I suppose that l3_hdr argument (and the last argument on line 569 too) should be "eth" instead? > > > Kind regards, > DanielPharos