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.7 required=3.0 tests=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 CAEA0C352A2 for ; Fri, 7 Feb 2020 10:18:08 +0000 (UTC) Received: from dpdk.org (dpdk.org [92.243.14.124]) by mail.kernel.org (Postfix) with ESMTP id 8780D20838 for ; Fri, 7 Feb 2020 10:18:08 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8780D20838 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=dpdk.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 2BE661C024; Fri, 7 Feb 2020 11:18:07 +0100 (CET) Received: from inbox.dpdk.org (xvm-172-178.dc0.ghst.net [95.142.172.178]) by dpdk.org (Postfix) with ESMTP id BDD8C1C011 for ; Fri, 7 Feb 2020 11:18:05 +0100 (CET) Received: by inbox.dpdk.org (Postfix, from userid 33) id 9E2F3A0542; Fri, 7 Feb 2020 11:18:05 +0100 (CET) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Fri, 07 Feb 2020 10:18:05 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: core X-Bugzilla-Version: 19.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: pavel.krauz@anritsu.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-dev] [Bug 393] rte_zmalloc_socket does not zero memory 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" https://bugs.dpdk.org/show_bug.cgi?id=3D393 Bug ID: 393 Summary: rte_zmalloc_socket does not zero memory Product: DPDK Version: 19.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: Normal Component: core Assignee: dev@dpdk.org Reporter: pavel.krauz@anritsu.com Target Milestone: --- Hello, It seems that rte_zmalloc_socket does not return zeroed memory on some case= s. It seems to work OK on all but HP G10 server where I was testing application that tried to create rte fragment table and do IP defragementation where it crashed on some of the structure members.=20 I put check into rte_zmalloc_socket to see if the memory was really zeroed = and it was not! Also if I zero the memory then the defragmentation works correc= tly and does not crash. I see from google that there were problems like this in the past with non zeroed rte_zmalloc_socket.=20 I have tested also the 19.02 version and it has same problem. this is on Centos 7.3 with linux kernel 3.10.0-514.el7.x86_64. Don't know if the linux itself can return non-zeroed memory in some case to dpdk lib. --=20 You are receiving this mail because: You are the assignee for the bug.=