From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 0BDFEA00C5 for ; Thu, 27 Oct 2022 19:35:02 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6B77841153; Thu, 27 Oct 2022 19:35:02 +0200 (CEST) Received: from mail-pj1-f50.google.com (mail-pj1-f50.google.com [209.85.216.50]) by mails.dpdk.org (Postfix) with ESMTP id 98BAF40146 for ; Thu, 27 Oct 2022 19:35:01 +0200 (CEST) Received: by mail-pj1-f50.google.com with SMTP id u8-20020a17090a5e4800b002106dcdd4a0so7221381pji.1 for ; Thu, 27 Oct 2022 10:35:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=VEZXoEbz5o+OSXExoCgxgJjXRrtiiqROy1bpVhsXRjY=; b=Nc4wzbWzDtF/L/+vWeb1uJiF1D1ZyLf0kpEjJ8ZD8FwEwK/vlw4DQdBKTaaf+PyjDs ukmUUlPY8FWrM7F4dYET/C9f7xYIOtr92W8VbioPqahdb5y49pSGXK7wjUYXaRNzDj03 Nv/JWSy40U/UZri/QioiZklz8A/MFJoKmBHUUmIsu9f3sofwu+oa5ThHipo2DaSrI4IU zN05syewxQhqZhCJtCZzXdB053Alg6xYAuy9BBJx/S5MC8KahIAbjAIeKsdrjxEdyA3l FbK1+WptLqff+iW9BjnARdU4yrZ8WITfyMUqkidHKB/uaKSsxY1EVdE9CM09FdLePhiu NjuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=VEZXoEbz5o+OSXExoCgxgJjXRrtiiqROy1bpVhsXRjY=; b=vvnJz/SF3Ye6DpgIUvbP1sRh/cTFH0DVTwCkhlL5MMto668YHyCsLOsGuyZI4/ceDh d5lLTh8mpsXNsJ9DV77EXOSHf1/nFtjWDiRDVcrD9MP1EtNG5nu396JlzjM49C0hFDMq q6kZsw7x1RoWrEcSmXJ9rAwB5gQqO3Eb5a13xRvkZ2V/8dY/BQkE4PmbEHLQbwakC1rv AP4fziH6FvXkLtl7BK73SqAJe5WCdqEisCRd3Eofumrtde7qZ2sGp4niMqnPLQkSX4Ws 9W/nJk/7gmt9c8mm/pKPXvvnHTh49TNEGQXMfZrHtm0fy1FX/0FRyfIgibgMtnefBrqx 06dw== X-Gm-Message-State: ACrzQf15wo3TZEGnuvWtqw+d2etyK2qO5eP/e6D5xs/kHpnojI5eslg/ 3auKrj/oeS5DO3Z2rgCWWLVb9w== X-Google-Smtp-Source: AMsMyM5xSC+L+qQP5ZbMaEdjLoeSE4PcjWY/SFoG0/829q34QFCidJNfCF4RANtRxAuElvlUsou0gw== X-Received: by 2002:a17:902:7b95:b0:178:ab50:76b5 with SMTP id w21-20020a1709027b9500b00178ab5076b5mr51235382pll.161.1666892100527; Thu, 27 Oct 2022 10:35:00 -0700 (PDT) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id p12-20020a170902e74c00b001754cfb5e21sm1506545plf.96.2022.10.27.10.34.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 27 Oct 2022 10:35:00 -0700 (PDT) Date: Thu, 27 Oct 2022 10:34:58 -0700 From: Stephen Hemminger To: Gokilavani A Cc: users@dpdk.org Subject: Re: rte_pktmbuf_alloc( ) returns same mbuf address which is not freed Message-ID: <20221027103458.16308900@hermes.local> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org On Tue, 25 Oct 2022 14:11:26 +0530 Gokilavani A wrote: > Hi, > > We have been blocked by this issue. > > Can anyone help us to resolve the issue? > > Thanks > Gokilavani A > > On Thu, Oct 13, 2022 at 4:39 PM Gokilavani A > wrote: > > > Hi, > > > > > > > > We are using *DPDK-19.11.11* for our application in which 4 construction > > threads construct packets periodically, place it in a circular queue and > > > > a transmission thread pushes that packet by reading that circular queue. > > > > > > In the long run, We are facing a crash in *eth_igb_xmit_pkts() *call > > which is called during transmission. > > > > > > After an inspect with GDB, we came to know that the non-freed mbuf address > > is returned by* rte_pktmbuf_alloc() *for another packet during > > construction, even though that mbuf is still not transmitted by the > > transmission thread, which makes the corresponding construction thread to > > update the same memory again. > > > > > > It is not clear why rte_pktmbuf_alloc() returns the mbuf pointer before > > that pointer is not getting freed by rte_eth_tx_burst() call?. > > > > > > We have created the mempool using the call, > > > > *rte_pktmbuf_pool_create(txMemPoolName, > > 16384,RTE_MEMPOOL_CACHE_MAX_SIZE,0, 2048 > > +RTE_PKTMBUF_HEADROOM, rte_eth_dev_socket_id(0));* > > > > > > Please guide us in resolving this issue. > > > > > > > > Thanks, > > > > Gokilavani A > > > > > > Looks like an application bug. Did you try building with every possible debug setting enabled. Things like MBUF_DEBUG and the address sanitizier.