From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 682F2A0032;
	Tue, 26 Oct 2021 14:09:11 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id D089C40E0F;
	Tue, 26 Oct 2021 14:09:10 +0200 (CEST)
Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178])
 by mails.dpdk.org (Postfix) with ESMTP id 64EB1407FF
 for <dev@dpdk.org>; Tue, 26 Oct 2021 14:09:10 +0200 (CEST)
Received: by inbox.dpdk.org (Postfix, from userid 33)
 id 4A4C1A0C47; Tue, 26 Oct 2021 14:09:10 +0200 (CEST)
From: bugzilla@dpdk.org
To: dev@dpdk.org
Date: Tue, 26 Oct 2021 12:09:10 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: DPDK
X-Bugzilla-Component: other
X-Bugzilla-Version: 21.11
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: konstantin.ananyev@intel.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: <bug-839-3@http.bugs.dpdk.org/>
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 839] pdump: any subsequent runs of pdump_autotest
 fail
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
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>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

https://bugs.dpdk.org/show_bug.cgi?id=3D839

            Bug ID: 839
           Summary: pdump: any subsequent runs of pdump_autotest fail
           Product: DPDK
           Version: 21.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: konstantin.ananyev@intel.com
  Target Milestone: ---

rte_pdump_init() always allocates new memzone for pdump_stats.
    Though rte_pdump_uninit() never frees it.
    So the following combination will always fail:
    rte_pdump_init(); rte_pdump_uninit(); rte_pdump_init();
    The issue was caught by pdump_autotest UT.
    While first test run successful, any consecutive runs
    of this test-case will fail like that:
RTE>>pdump_autotest
IN PRIMARY PROCESS
rte_pdump_init(): cannot allocate pdump statistics
rte_pdump_init failed
...

I submitted fix to free pdum_stats memzone at rte_pdump_uninit():
https://patches.dpdk.org/project/dpdk/patch/20211026115301.5456-1-konstanti=
n.ananyev@intel.com/

If you think it is not a proper way (instead we should keep memzone forever=
, or
so),
please feel free to supersede my patch with newer one.

--=20
You are receiving this mail because:
You are the assignee for the bug.=