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 4BF6C46BD9 for ; Mon, 21 Jul 2025 13:39:24 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3F3FE40650; Mon, 21 Jul 2025 13:39:24 +0200 (CEST) Received: from mail-pg1-f171.google.com (mail-pg1-f171.google.com [209.85.215.171]) by mails.dpdk.org (Postfix) with ESMTP id C2BD34021E for ; Mon, 21 Jul 2025 13:39:21 +0200 (CEST) Received: by mail-pg1-f171.google.com with SMTP id 41be03b00d2f7-b390d09e957so4488517a12.1 for ; Mon, 21 Jul 2025 04:39:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uetpeshawar-edu-pk.20230601.gappssmtp.com; s=20230601; t=1753097961; x=1753702761; 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=MkJxfN0T4T5iQJcj2T4EaSzrA7mQRtGtqYbIznmpc1s=; b=Jw4di5pdDp2k20M4iKi0gr7edUlBTVkgc1vVxQ1wXv/ke6ZWB1avLBjwiMRmk6sSw/ 1cWRg2SMN80QFbO+bLOR8RJdhZ08vesV5ulcvMwwy/fl1CpENXZ7ZIbZ8TfQc0XrM088 mp0IQ26Gp7LG3jC0OKV0JXCzCsZksE9mY/iRgQsiHyRjHB31ihy3Lk7CGCpx0WAEFbIs zlnCtneiqxzexrGFtwqym5mGyluImpMtDNv+bRXrbZxesEFgFN7oHJh5z6hPXkkh/Kl+ fwhU8uebPzadXQxvWDnkzY7KOuM4H43vko6bXmJf/7LObwlk5DDRhjJ5lePsWqaVRXlO 2OMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1753097961; x=1753702761; 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=MkJxfN0T4T5iQJcj2T4EaSzrA7mQRtGtqYbIznmpc1s=; b=WpLxfacIyWkfr9Sb+CEZt2SxJR0xj4Akyd4f9QL5fW5la8AZniXqZojLGeeCroZVCs 7YDxZayQtFpEp2sL2gYnrBrGyJF2tUF9nO367+TrSMjnES0nfE5D1mB44JwgqYWoC1aS fWp4dqCcGapyuUFZ7wGa0GWwimOl2u+K5VNMaBIBnx944dLwVEOe6WuXOCf8/LdK/A/9 CMpe9Z6c9yCypAninwsmOqLMfuP462tSg8HSBYyEbTzz9UuMH66byNn6DXvNtFc2kFu6 BRXkuQVmRq21WUVDcrD+J33OuAda8FrZFfzY0tb8xKiXVB5q2YXDuxDJ97vbq5dcs21C nA1Q== X-Forwarded-Encrypted: i=1; AJvYcCXaZzsXXK3dQ32n50BGY8U6FbgqLlA8ZKe0bCi/5eQK3x3Lgf78t6btMM3f78p+3sm0wsoQG8w=@dpdk.org X-Gm-Message-State: AOJu0YzHNKyWHQ5duMiBOxCokOXOGYpKt5h5KHxIKGFWdpzzP78pIyaN bQF/Fs0GOWtzNBQ9QKYeEZQ/d29CsFTNaWFcKizsFRKbzODVmS2jUPSE2GMKKhnUjoo= X-Gm-Gg: ASbGncsp5hGNXeK0so3hRowdDC6DQrKdMd7hTmytAJyJ+93a6QBy6BrQFPfeiPS9jo9 c2fx7R6cW8znBQ7pUSzylxe4FpZoAL/t8TqRfOHPyAoshIq7aGJkgZJ9KCQaHdxnltZJWVS5T7C bHbjNcEd2SFnRH+29JK7cJ27ueVHf53enXSQntHYuheXdv4GF7IxhfcG6e1T37yds+j0dl3AHxc DKjl/c0f2DevlRmSkvymzdegwoef31bAyHrtKNC3oWuNykWhiAssBzjoHhN45smaiGotI0Gp5lo WOirVYmnP4EBYxa/9QrO/P/MTD5QcMAtEO7jyR6Y3OeB1X1C0Ut2qZiywf11qvHrmto6/5WN2SX jj1Lr8I1mh1QFovSOYZZaMWZKWHR4gmL7rHAC3KQ4Vo2NA4NH X-Google-Smtp-Source: AGHT+IF0PqcMHCotoOXGGv5n7pa/ezlsgr6ztLyJspn2wcyjQJ9Sup+wHTc/8QtSy14eCDKVwaj7lw== X-Received: by 2002:a17:90b:4f49:b0:31a:b92c:d679 with SMTP id 98e67ed59e1d1-31c9f44e3c1mr27858770a91.35.1753097960797; Mon, 21 Jul 2025 04:39:20 -0700 (PDT) Received: from localhost.localdomain ([64.62.143.197]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-31cc3f2e215sm6035428a91.33.2025.07.21.04.39.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 21 Jul 2025 04:39:20 -0700 (PDT) From: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk> To: dsosnowski@nvidia.com, thomas@monjalon.net, andrew.rybchenko@oktetlabs.ru Cc: dev@dpdk.org, rasland@nvidia.com, stable@dpdk.org, viacheslavo@nvidia.com, orika@nvidia.com, suanmingm@nvidia.com, matan@nvidia.com Subject: Re: [PATCH] net/mlx5: fix crash when using meter in transfer flow Date: Mon, 21 Jul 2025 07:38:12 -0400 Message-ID: <20250721113822.1029342-1-14pwcse1224@uetpeshawar.edu.pk> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20250721105819.2ci66fl7bzikwb22@ds-vm-debian.local> References: <20250721105819.2ci66fl7bzikwb22@ds-vm-debian.local> MIME-Version: 1.0 Content-Type: text/plain; charset=y Content-Transfer-Encoding: 8bit X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Hi Dariusz, Thanks for the feedback. Agreed, this check only papers over a deeper issue with multi-process lifecycle in ethdev. If the primary process exits after freeing ethdev data, all subsequent PMD-level calls (e.g., dev_infos_get) in secondary are inherently unsafe due to dangling pointers. Unless ethdev explicitly invalidates the port (or secondary process detects primary exit), the current behavior results in use-after-free regardless of PMD. For now, this patch avoids a crash in one case (dev_infos_get), but long-term a proper ethdev-level solution is needed — either by: - Marking ports invalid on primary exit, - Notifying secondaries to teardown, - Or refusing API access after shared data disappears. Until then, we can keep this as a safety patch to prevent segfaults in common test scenarios.