From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 856A3A0487 for ; Tue, 30 Jul 2019 10:50:21 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 3DAE51BFDC; Tue, 30 Jul 2019 10:50:21 +0200 (CEST) Received: from new4-smtp.messagingengine.com (new4-smtp.messagingengine.com [66.111.4.230]) by dpdk.org (Postfix) with ESMTP id 2C0381BFDB; Tue, 30 Jul 2019 10:50:20 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id A1D3E1C6A; Tue, 30 Jul 2019 04:50:19 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 30 Jul 2019 04:50:19 -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=5uQXikU7/Yq3JXbi/vAXDONZi+F0c8UsBMq9PVzh/gY=; b=lXjfz7dTtyFj qkdmF+wtLKHkI2FoujTTH/HJB0cTywQfP0FnMoZkqrwnsIQoF80veQ7LTTAtv/Vt IG/9rugiTUZGpjvaB7y71KVBCP4lJM37smM14BZAawh02T3SOU3YOqGb1Q32rrOK 7dy0njP1HGSMBPuGpJzvq+34YlCo0sA= 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=fm3; bh=5uQXikU7/Yq3JXbi/vAXDONZi+F0c8UsBMq9PVzh/ gY=; b=UP8bGF+ulbvMlExUYPcPFw/yhiKDahQhyI2Lwq/usYV3G3LDWqm19oDo5 L6QEYPIMb5m3vnunMVRqgXnaDl3d/EdFKQEHqIXvFxq+HWKhhKHHNzajv1g4pMCp LJiRscE4LiKEEk/KEgXtXIfPwL2keYOsKwIMIha01nu1Egv3ZiXdNETFwpQkLw14 SIcJ1xcb0VtigdJDhU0z4jh7nqBsNr3TbYdBHIaFm7L0mMDJ8JVunKIcHmbWo1oW 8q6VEvbZvzAESrFtVh2He82kYCcshuijnATtyM5IFvaXpFJDCL0gj/fBVUZ6Q/AP GnEO38XNFf4+zY7tqCdTAb/ZdVVZA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrleefgddtjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd 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 4558C8005C; Tue, 30 Jul 2019 04:50:15 -0400 (EDT) From: Thomas Monjalon To: dev@dpdk.org Cc: stable@dpdk.org, hgovindh , Marko Kovacevic , Ori Kam , Bruce Richardson , Pablo de Lara , Radu Nicolau , Akhil Goyal , Tomasz Kantecki , drc@linux.vnet.ibm.com, ruifeng.wang@arm.com, maciej.czekaj@caviumnetworks.com Date: Tue, 30 Jul 2019 10:50:14 +0200 Message-ID: <2414234.RRTHkAQoda@xps> In-Reply-To: <20190726135858.55792-1-hariprasad.govindharajan@intel.com> References: <20190726132758.55217-1-hariprasad.govindharajan@intel.com> <20190726135858.55792-1-hariprasad.govindharajan@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v4] examples/l3fwd: fix unaligned memory access 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" Review please? 26/07/2019 15:58, hgovindh: > Fix unaligned memory access when reading IPv6 header which > leads to segmentation fault by changing aligned memory read > to unaligned memory read. > > Bugzilla ID: 279 > Fixes: 64d3955de1de ("examples/l3fwd: fix ARM build") > Cc: maciej.czekaj@caviumnetworks.com > Cc: stable@dpdk.org > Signed-off-by: hgovindh > --- a/examples/l3fwd/l3fwd_em.c > +++ b/examples/l3fwd/l3fwd_em.c > +#if defined RTE_ARCH_X86 > + key.xmm[1] = _mm_loadu_si128(data1); > +#else > key.xmm[1] = *(xmm_t *)data1; > - > +#endif