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 DF58346130; Fri, 24 Jan 2025 19:18:39 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 871CC42E51; Fri, 24 Jan 2025 19:17:38 +0100 (CET) Received: from mail-pl1-f172.google.com (mail-pl1-f172.google.com [209.85.214.172]) by mails.dpdk.org (Postfix) with ESMTP id 50DEB42DBD for ; Fri, 24 Jan 2025 19:17:30 +0100 (CET) Received: by mail-pl1-f172.google.com with SMTP id d9443c01a7336-2161eb94cceso30575765ad.2 for ; Fri, 24 Jan 2025 10:17:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1737742649; x=1738347449; darn=dpdk.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=gXc6GdnGLjClOheepz36rNyvJcr3sEnmXYCrvGSLx7o=; b=h6RLvAOEM3SXusWXnzIS///EhBPezVcRo26TFW9WFClkYlvsIMo5QqK868T+mckkCl mVvIYoML/OhZqUiaejEx8JbxPEPsojXKA49ocqa6x2xxMSIkrLkjwwsBPWvX3HnGE+dD q0ezYE5CxyJcJaHyNQQtYSvDW9DgTceV94Hh27nPCdkIrkC0p5FZE1/v4eRduTBwQXDU AzmJGvDF2KUkOfsUBm5xtHqN/XHtH9XGcDXHBL8js8WUAz4bdnj9zthJKXFD1m4GZcSk BUzykrqjzabA0CanZF12yp2Pc1CQKTA97CA9bfKU3mqrnqBZMTNeKruxl5Ul6SZX6pOL xFuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1737742649; x=1738347449; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=gXc6GdnGLjClOheepz36rNyvJcr3sEnmXYCrvGSLx7o=; b=gv3wuUxFj9vyHPGcYLiS4l/GSsVwy0dvsiPEqN6Fpgpm+GqXUO78FUcZBoEBKlkcFD yRrUY3ZAM8BLwcyOk3DxC+ZWLIqVtq8TwQjdn77k/46Z5KYxDVRf7dkgqQE5WJzO+sg6 EQxRrA48BS4gEZ8wQQWZjB6zYqowKmCwdBlrMBAP1U9xX0On2QHoYmJepIsSIZeGbBU1 x16wUB6eekicH7cjRW4kbYcj2Zn9X1A1FGMMvaNwJGmE8sTCCTSi8RAcLi0F2kKWn6i6 gzaxh6tIYP3k46lEBIeXCWCSalBQyoJf2Q2rt+244L7w10IbASdCZN5LKsO2PcA8lNwn ngnQ== X-Gm-Message-State: AOJu0Yy8AS4vrTuSFxDxLBDHfhXDmYh9U0yFEQ/ywlZgXn7/H3KyNQzR I6X8y3Yg7ZSBFKUNwiep9eS5kib7OdMF8OKRC3dVV54MqhhADv+h8CwhTbbbLuk+HdAq1Xb5oNn m X-Gm-Gg: ASbGncvBwotRuN3PrN44kX60ZCHVl0GSATCTcjs8e1FNt0et2bGBKIJMZYSx17jkP/H z65JVaA/CZAiyhVbWkYCivCCRohNmPEHDnS0928w7gQJsbJtnzBvLn4Np6mh6+xGvd15AcKqbFP 1ubrkMEjdO6JqmtJNcUUoeAI48e/dq2sen/ZWk3cTPmzNYelniJaoghPm7arMjrM7bCgTaS98FY 2ArJdJVUwpj8OO6ISWd6wsOLWBSxYfeHXRIjP2AHtDrWiQ70SvCEEkLaQUmUcbQyy7HCMHbeTnK CiE9tz2PQryt6eF8Xh1mNtRcLMkmmlw8SVVU+nl4+AVTI+i1v8XJzvv9IA== X-Google-Smtp-Source: AGHT+IEFE1Ac8RHU6xmK6oZAPy63xGFO4uyZ+V4+smg0HKAL5KU17Ff3ssEvEJph5gTwCsij0C8UCw== X-Received: by 2002:a05:6a20:430e:b0:1e1:9f24:2e4c with SMTP id adf61e73a8af0-1eb2147fd19mr43260302637.16.1737742649641; Fri, 24 Jan 2025 10:17:29 -0800 (PST) Received: from hermes.local (204-195-96-226.wavecable.com. [204.195.96.226]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-72f8a6b2ed8sm2184477b3a.41.2025.01.24.10.17.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 24 Jan 2025 10:17:29 -0800 (PST) From: Stephen Hemminger To: dev@dpdk.org Cc: Stephen Hemminger Subject: [PATCH v4 16/16] doc: add release note about allocation attributes Date: Fri, 24 Jan 2025 10:15:07 -0800 Message-ID: <20250124181704.86567-17-stephen@networkplumber.org> X-Mailer: git-send-email 2.45.2 In-Reply-To: <20250124181704.86567-1-stephen@networkplumber.org> References: <20250110170603.538756-1-stephen@networkplumber.or> <20250124181704.86567-1-stephen@networkplumber.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Since many functions now have allocation attribute, add a release note to inform users. Signed-off-by: Stephen Hemminger --- doc/guides/rel_notes/release_25_03.rst | 30 ++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/doc/guides/rel_notes/release_25_03.rst b/doc/guides/rel_notes/release_25_03.rst index 85986ffa61..95ccc01133 100644 --- a/doc/guides/rel_notes/release_25_03.rst +++ b/doc/guides/rel_notes/release_25_03.rst @@ -63,6 +63,36 @@ New Features and even substantial part of its code. It can be viewed as an extension of rte_ring functionality. +* **Hardened of more allocation functions.** + + Added allocation attributes to functions that allocate data: + * ``rte_stats_bitrate_create()`` + * ``rte_sched_port_config()`` + * ``rte_ring_create()`` + * ``rte_tel_data_alloc()`` + * ``rte_rib_create()`` + * ``rte_rib6_create()`` + * ``rte_reorder_create()`` + * ``rte_mempool_create()`` + * ``rte_member_create()`` + * ``rte_acl_create()`` + * ``rte_comp_op_pool_create()`` + * ``rte_event_ring_create()`` + * ``rte_fib_create()`` + * ``rte_fib6_create()`` + * ``rte_lpm_create()`` + * ``rte_lpm6_create()`` + * ``rte_fbk_hash_create()`` + * ``rte_hash_create()`` + * ``rte_port_in_action_profile_create()`` + * ``rte_port_in_action_create()`` + * ``rte_table_in_action_profile_create()`` + * ``rte_table_in_action_create()`` + + This can catch some obvious bugs at compile time (with GCC 11.0 or later). + For example, calling ``free`` on a pointer that was allocated with one + of those functions (and vice versa); freeing the same pointer twice + in the same routine or freeing an object that was not created by allocation. Removed Items ------------- -- 2.45.2