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 13F6042D07;
Tue, 20 Jun 2023 13:51:15 +0200 (CEST)
Received: from mails.dpdk.org (localhost [127.0.0.1])
by mails.dpdk.org (Postfix) with ESMTP id F32C740DDA;
Tue, 20 Jun 2023 13:51:14 +0200 (CEST)
Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178])
by mails.dpdk.org (Postfix) with ESMTP id 50247400D6
for <dev@dpdk.org>; Tue, 20 Jun 2023 13:51:13 +0200 (CEST)
Received: by inbox.dpdk.org (Postfix, from userid 33)
id 4749E42D08; Tue, 20 Jun 2023 13:51:13 +0200 (CEST)
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1256] drivers/common/mlx5: mlx5_malloc() called on invalid
socket ID when global MR cache is full and rte_extmem_* API is used
Date: Tue, 20 Jun 2023 11:51:13 +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: baciumariuscristian@yahoo.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-1256-3@http.bugs.dpdk.org/>
Content-Type: multipart/alternative; boundary=16872618730.F9C007f.2160258
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
MIME-Version: 1.0
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
--16872618730.F9C007f.2160258
Date: Tue, 20 Jun 2023 13:51:13 +0200
MIME-Version: 1.0
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
https://bugs.dpdk.org/show_bug.cgi?id=3D1256
Bug ID: 1256
Summary: drivers/common/mlx5: mlx5_malloc() called on invalid
socket ID when global MR cache is full and
rte_extmem_* API is used
Product: DPDK
Version: 21.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: baciumariuscristian@yahoo.com
Target Milestone: ---
Overview:
Attempt to allocate a new mlx5 MR entry when global Btree cache is full end=
s up
calling mlx5_malloc with the EXTERNAL_HEAP_MIN_SOCKET_ID socket ID, given t=
hat
no external-memory heap has been created. Instead the rte_extmem_* API is u=
sed.
Steps to reproduce:
- start a primary DPDK process, on a NIC compatible with mlx5_core driver;
- use rte_extmem_register() to register >512 pages of 4KB;
- use rte_dev_dma_map() to dma-map each page;
- rte_eth_tx_burst() an mbuf with an external buffer from the last page of =
the
registered memory (or a page above index 512). (a virtual address that will=
not
be found in the global Btree cache);
Actual results:
mlx5_malloc in mlx5_mr_create_primary() fails with "Unable to allocate memo=
ry
for a new MR". From this point forward, packets never reach the other end.
Expected results:
MR entries should be successfully retrieved from backup or created when cac=
he
becomes full; calling mlx5_malloc() on external heap socket should not be
possible when rte_extmem_* API is used. As it is stated in the DPDK
documentation[1], "Memory added this way will not be available for any regu=
lar
DPDK allocators".
Build Date & Hardware:
20 Jun 2023 on Debian GNU/Linux 4.18.0
[1]: https://doc.dpdk.org/guides-21.11/prog_guide/env_abstraction_layer.html
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--16872618730.F9C007f.2160258
Date: Tue, 20 Jun 2023 13:51:13 +0200
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
<html>
<head>
<base href=3D"https://bugs.dpdk.org/">
</head>
<body><table border=3D"1" cellspacing=3D"0" cellpadding=3D"8" class=3D"=
bz_new_table">
<tr>
<th>Bug ID</th>
<td><a class=3D"bz_bug_link=20
bz_status_UNCONFIRMED "
title=3D"UNCONFIRMED - drivers/common/mlx5: mlx5_malloc() called on inva=
lid socket ID when global MR cache is full and rte_extmem_* API is used"
href=3D"https://bugs.dpdk.org/show_bug.cgi?id=3D1256">1256</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>drivers/common/mlx5: mlx5_malloc() called on invalid socket I=
D when global MR cache is full and rte_extmem_* API is used
</td>
</tr>
<tr>
<th>Product</th>
<td>DPDK
</td>
</tr>
<tr>
<th>Version</th>
<td>21.11
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux
</td>
</tr>
<tr>
<th>Status</th>
<td>UNCONFIRMED
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>Normal
</td>
</tr>
<tr>
<th>Component</th>
<td>other
</td>
</tr>
<tr>
<th>Assignee</th>
<td>dev@dpdk.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>baciumariuscristian@yahoo.com
</td>
</tr>
<tr>
<th>Target Milestone</th>
<td>---
</td>
</tr></table>
<p>
<div class=3D"bz_comment_block">
<pre class=3D"bz_comment_text">Overview:
Attempt to allocate a new mlx5 MR entry when global Btree cache is full end=
s up
calling mlx5_malloc with the EXTERNAL_HEAP_MIN_SOCKET_ID socket ID, given t=
hat
no external-memory heap has been created. Instead the rte_extmem_* API is u=
sed.
Steps to reproduce:
- start a primary DPDK process, on a NIC compatible with mlx5_core driver;
- use rte_extmem_register() to register >512 pages of 4KB;
- use rte_dev_dma_map() to dma-map each page;
- rte_eth_tx_burst() an mbuf with an external buffer from the last page of =
the
registered memory (or a page above index 512). (a virtual address that will=
not
be found in the global Btree cache);
Actual results:
mlx5_malloc in mlx5_mr_create_primary() fails with "Unable to allocate=
memory
for a new MR". From this point forward, packets never reach the other =
end.
Expected results:
MR entries should be successfully retrieved from backup or created when cac=
he
becomes full; calling mlx5_malloc() on external heap socket should not be
possible when rte_extmem_* API is used. As it is stated in the DPDK
documentation[1], "Memory added this way will not be available for any=
regular
DPDK allocators".
Build Date & Hardware:
20 Jun 2023 on Debian GNU/Linux 4.18.0
[1]: <a href=3D"https://doc.dpdk.org/guides-21.11/prog_guide/env_abstractio=
n_layer.html">https://doc.dpdk.org/guides-21.11/prog_guide/env_abstraction_=
layer.html</a>
</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
<div itemscope itemtype=3D"http://schema.org/EmailMessage">
<div itemprop=3D"action" itemscope itemtype=3D"http://schema.org/Vi=
ewAction">
=20=20=20=20=20=20=20=20=20=20
<link itemprop=3D"url" href=3D"https://bugs.dpdk.org/show_bug.cgi=
?id=3D1256">
<meta itemprop=3D"name" content=3D"View bug">
</div>
<meta itemprop=3D"description" content=3D"Bugzilla bug update notif=
ication">
</div>
</body>
</html>=
--16872618730.F9C007f.2160258--