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 A369FA0560 for ; Mon, 21 Nov 2022 15:12:37 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9CE734161A; Mon, 21 Nov 2022 15:12:37 +0100 (CET) Received: from mail-qt1-f171.google.com (mail-qt1-f171.google.com [209.85.160.171]) by mails.dpdk.org (Postfix) with ESMTP id 55506400EF for ; Mon, 21 Nov 2022 15:12:36 +0100 (CET) Received: by mail-qt1-f171.google.com with SMTP id h21so7286008qtu.2 for ; Mon, 21 Nov 2022 06:12:36 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=yc84dERtSg0ltusKH/kQqQPD/t6OKWR+gLXGR/AwDQ4=; b=m7LY5KW0xnHSyWp60+KqiBrnH8ApprdfAgji8WxowgrPGOXCrdEXMEB30+tdmPl7M6 iyi76FZLStUF2eoTbWqnU2JaY2VQ0VJoVVk38FmsQOzURVhU/SJ5dYvnsNEGHNqzt3k4 F78QsAfMMQ/BErE9/wRqOAAsE+visThX68O+Li78qKn+h4tFLJPZkd68nDMGgCIEVYLC XXVHjXYDYrHe706Kgfz/czrfoij+m9+kGJVLSunSUgQF+WapJC0Bv+0ResL1lLGnc/5e rZc3FAK5Uucy9l/F0dbr4My9p1OI5oxJMyYWnZ+6GYytzIL6c9FX6fqYd3WMeuITScP0 4EXQ== X-Gm-Message-State: ANoB5pkZzod40MtIbV/7xbwHq+ehPyrBCw/p9+BALTJfYvLWJe00WeqF uUfgR7GijCoSaLXTMYmcqWKyXcjuLDkDyA== X-Google-Smtp-Source: AA0mqf7xlDwqchkKiZeSO36qHo1gf2gCJbAJwI2mhQglUoOuhy2QwZEYIPD7CEImDmCymo3+ZWBZhg== X-Received: by 2002:ac8:4d0e:0:b0:39d:11a9:760d with SMTP id w14-20020ac84d0e000000b0039d11a9760dmr17127939qtv.139.1669039955497; Mon, 21 Nov 2022 06:12:35 -0800 (PST) Received: from mail-yw1-f171.google.com (mail-yw1-f171.google.com. [209.85.128.171]) by smtp.gmail.com with ESMTPSA id n1-20020a05620a294100b006fa617ac616sm8369062qkp.49.2022.11.21.06.12.35 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 21 Nov 2022 06:12:35 -0800 (PST) Received: by mail-yw1-f171.google.com with SMTP id 00721157ae682-36cbcda2157so114073577b3.11 for ; Mon, 21 Nov 2022 06:12:35 -0800 (PST) X-Received: by 2002:a0d:ea8c:0:b0:345:8b:ee67 with SMTP id t134-20020a0dea8c000000b00345008bee67mr17310132ywe.425.1669039954835; Mon, 21 Nov 2022 06:12:34 -0800 (PST) MIME-Version: 1.0 References: <20221105171146.1520039-47-luca.boccassi@gmail.com> <20221117230859.611465-1-luca.boccassi@gmail.com> <20221117230859.611465-16-luca.boccassi@gmail.com> <8ed59648a36cc2d55db9a822f3cf9023d7805c92.camel@debian.org> In-Reply-To: From: Luca Boccassi Date: Mon, 21 Nov 2022 14:12:23 +0000 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: patch 'net/mlx5: fix port event cleaning order' has been queued to stable release 20.11.7 To: Michael Baum Cc: Matan Azrad , dpdk stable Content-Type: text/plain; charset="UTF-8" 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 On Sun, 20 Nov 2022 at 07:28, Michael Baum wrote: > > On Fri, 2022-11-18 at 16:28, Luca Boccassi wrote: > > > > On Fri, 2022-11-18 at 12:53 +0000, Michael Baum wrote: > > > Hi Luca, > > > > > > This patch causes another issue, so I have sent another patch to squash into. > > > > > > The title of this patch is: " [PATCH 20.11] net/mlx5: fix invalid memory access > > in port closing" > > > > > > Thanks, > > > Michael Baum > > > > Is it a backport gone wrong (or an issue specific to 20.11), or is it an issue also in > > the same change that went in main? If the latter, what's the commit id of the > > fix? > > The issue also in the same change that went in main. > I sent the fix and it isn't merged yet, the fix in patchwork: https://patchwork.dpdk.org/project/dpdk/patch/20221117152807.1259256-1-michaelba@nvidia.com/ Is this going to be pulled in 22.11?