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 D1EC946C4A for ; Wed, 30 Jul 2025 07:07:19 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C35FE40DD1; Wed, 30 Jul 2025 07:07:19 +0200 (CEST) Received: from mail-pf1-f173.google.com (mail-pf1-f173.google.com [209.85.210.173]) by mails.dpdk.org (Postfix) with ESMTP id 1C54B40668 for ; Wed, 30 Jul 2025 07:07:17 +0200 (CEST) Received: by mail-pf1-f173.google.com with SMTP id d2e1a72fcca58-74264d1832eso7414839b3a.0 for ; Tue, 29 Jul 2025 22:07:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uetpeshawar-edu-pk.20230601.gappssmtp.com; s=20230601; t=1753852036; x=1754456836; 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=OOVLq4LIkeQwRFOTJyk5/7dxT4AVmK7qMvefoffPBFs=; b=CyCotyqfPqiKJ7RgjktOtrfGlso7wVGUN67I+d2SuW9Br6dJq3dHpcmmAOijhZUco2 zAC/BeZd27pN7BxkEpDyoeHlcXPB7A/A213GsxQBt9S50j6eniQy/83eWY6GrWlFpgZ6 1RhOOXwn0ixAihUjmCWIqBfTS0SZhvOVcc7jwmjjDyE2IlxYkIGhBUPl7Zc6duHZqIme gYNJRIbI7YZlEnX17jBIAG6HbDrB4rWt0B6cmh4yzSKESNDAnMnnqDM6bgIzqS4esukG SEokusb6IMo3EozjOVX25cHAu0mCZW66uvXTnYEFUS5sck678addgW4yIMPhz/V+7827 ovIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1753852036; x=1754456836; 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=OOVLq4LIkeQwRFOTJyk5/7dxT4AVmK7qMvefoffPBFs=; b=HKhzvc0h2PLyyH0NprTQnx0vuZPnkNqS+H1ITc6nPjN03RXAkzwesqIwDeDh+XDUKf yIAUvb03GMtMk/Q28Jvhj2Zx/2MTClovuZCfdIhmLiTJ9Awp8YPCmGVPAh/GclwgA52m KMba+hvp8kfY0fo7hYMrrpoadhN2Rm3qHZPHDWy+0L4zz2Zdwf0tJaBmsEOiNjk4g5E/ AkBtJ61ruvTeTFSfcxnzNCQGV1UlV63dSyuy3PnlpplWzkiWAtlML+5KdePGron2YRqv snT1RhlanZQGFA8Y01Fznz7JC05xrc8dd4mG8jNUYsi4iPUZq2w4yTfog0O21b8MifDe Sbuw== X-Forwarded-Encrypted: i=1; AJvYcCVWjjHUyc1847Dk1fcjfNTYCY/CBYLkueKsPTUdJc6zu0JsJ9CASLXlVX0Nktk0kLsIMUWzmBQ=@dpdk.org X-Gm-Message-State: AOJu0YznYSqJ49E9GenOZ3UmYLMj+RJqGF7Xx2+ifeN+FXxPk+bTxxIm jqB6cukh9mDpUD/SZl2IAlaKU3FLeH5sEVjE7GKYkSGk+s+7P1H2HSOYT/cz5ftMMCU= X-Gm-Gg: ASbGncvtxJw8ynjGy6DQXzUh6l7V8+Fkd3GtqRyTjfgAyc69hqehr+WzeqpTh326tWB SBhtgI6aWen37cXsWKOPybQpdbX0biGMBbv3nQB/M7LwjDahR2byIcuQCjef9IjLcTV6VpetmOs rT2Xqsuf+ZWtk4JseZg9JsZiM8+Cr3UIomTOPO4ES9L19A0rhW0NLUqVgK8WDx7aHHh9FXCrdpD 6OhZltRLVkAiyNhVH1kHYojJCiAJODkhK+/wKW1ZA0Qvk/BWaCdXrfSNQGRPi7BGVwvsO3SMHUA GVke+aqSlp+PMBFXn0vBLFmF526qDzdZH/v/K18m6uVi4cmWMapU9abvNfUIwzyR0puyf/80fPT mZdo5W0M8n0w3xNN36N//V8W4eg2zsxA4QQlyae24IwtiAkps X-Google-Smtp-Source: AGHT+IGr9xs4kNDiUXJYLSFSKi2aZzD5C0l2ANoUZNrqajOWC1HHeLtgu+4NfX2i28c+Mk8pqmgYiw== X-Received: by 2002:a05:6a00:844:b0:75f:7a4d:ea11 with SMTP id d2e1a72fcca58-76ab2946b13mr2680323b3a.11.1753852036076; Tue, 29 Jul 2025 22:07:16 -0700 (PDT) Received: from localhost.localdomain ([64.62.143.197]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-7640b3d3d3csm9515124b3a.111.2025.07.29.22.07.15 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 29 Jul 2025 22:07:15 -0700 (PDT) From: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk> To: stephen@networkplumber.org, thomas@monjalon.net, ferruh.yigit@amd.com, andrew.rybchenko@oktetlabs.ru Cc: dev@dpdk.org, stable@dpdk.org Subject: Re: [PATCH] [PATCH v4] lib/ethdev: fix segfault in secondary process by validating dev_private pointer Date: Wed, 30 Jul 2025 01:07:02 -0400 Message-ID: <20250730050702.74381-1-14pwcse1224@uetpeshawar.edu.pk> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20250729143420.0fd7b627@hermes.local> References: <20250729143420.0fd7b627@hermes.local> MIME-Version: 1.0 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 Stephen, Many thanks for diving deeper into the issue and sharing the insights. I agree. given that the primary tears down all the devices on exit, the secondary is left with dangling pointers and inconsistent state. Without a mechanism to notify or synchronize that teardown, I think it is the only option for the secondary to exit immediately, without attempting any cleanups, once it detects the primary has exited. Best regards, Khadem