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 AD223A00C2 for ; Tue, 3 Jan 2023 15:02:45 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A359740693; Tue, 3 Jan 2023 15:02:45 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 44C3940689 for ; Tue, 3 Jan 2023 15:02:44 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1672754563; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=anAgeYdNRzpetT0oz8MbLscNGv143+UPnilwGi7eiCQ=; b=UphEN70uR1vDl9f+Ud64tv7gcpXiKS+hAfiRz2LpU6sRQvBKccRm5+aXo5HOV0/JSYkXmi H92pqrtbK3bWYDs84it7Hka/E8qCYvl1+2dZHHQj22kYD88r+zrsmQmNgAn23n4jDry8uu 0pFQy4MDLzVbJuD/c7lkD3rD1XVxX+Y= Received: from mail-pf1-f198.google.com (mail-pf1-f198.google.com [209.85.210.198]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-275-RND6LaFvPCaRWYbErHNx7Q-1; Tue, 03 Jan 2023 09:02:42 -0500 X-MC-Unique: RND6LaFvPCaRWYbErHNx7Q-1 Received: by mail-pf1-f198.google.com with SMTP id bq10-20020a056a000e0a00b00581221976c0so9844374pfb.10 for ; Tue, 03 Jan 2023 06:02:42 -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=anAgeYdNRzpetT0oz8MbLscNGv143+UPnilwGi7eiCQ=; b=B/Y0P8hWKRO+NhD19bfaTP1L/+wN/ojmbi/kG0MATBSX+KArR9SsIsMUjN/4MBZX51 Sve3grCl0fAJRB/OsdLO3sgzYw4ZumlpxZMm2nTOg5Xj1EyARYf1N0yiveK2RgSm429h DObAYXExbXI1Z8QqZHElkvh97+dS9Q5nnz57Ub+fD0KcaZovkuSNyAV1bllQkF/KJzN5 EU75+qAMZYk20yIrIkyOuVTDK+ipmJFRzc9lFEgTVZD8QaADx65onoQSNmrLBHL2X104 eQuxU0IBhTX941NTRL7tGIoyjjllfLt8kTYxodqbiTRSoYgPr3LJiED0Wky8j2UANgEb bffw== X-Gm-Message-State: AFqh2krFSbf49orcP9umJzrRu+HhvNpEW+fHmXL11JMXuFtRYZZbwvv4 WozhZhgGOZOTIu1TwbYtf/CHDoMnRMQnMEElybqLvz+Qo4bToUlBAd7io3TwXVCC86m4Vhke7k+ jeMVtO6ajv7ren8XeOYlqHu4= X-Received: by 2002:a17:90b:264d:b0:226:1564:643c with SMTP id pa13-20020a17090b264d00b002261564643cmr1594890pjb.206.1672754561380; Tue, 03 Jan 2023 06:02:41 -0800 (PST) X-Google-Smtp-Source: AMrXdXv07h2bREJHf2XcVfKk+RFiAvxW30cj5q9+TevKDr+m/y0rTXcv1HfvR0FOkOwd4V8+aVHdJEzTCVc0zIsEuik= X-Received: by 2002:a17:90b:264d:b0:226:1564:643c with SMTP id pa13-20020a17090b264d00b002261564643cmr1594881pjb.206.1672754560944; Tue, 03 Jan 2023 06:02:40 -0800 (PST) MIME-Version: 1.0 References: <20221212143715.29649-1-david.marchand@redhat.com> <20221213091837.87953-1-david.marchand@redhat.com> In-Reply-To: <20221213091837.87953-1-david.marchand@redhat.com> From: David Marchand Date: Tue, 3 Jan 2023 15:02:29 +0100 Message-ID: Subject: Re: [PATCH v2] net/i40e: don't check link status on device start To: Yuying Zhang , Beilei Xing Cc: dev@dpdk.org, stable@dpdk.org, Qi Zhang , Dapeng Yu , Wenxuan Wu , Jie Wang X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com 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 Hi i40e maintainers, On Tue, Dec 13, 2022 at 10:19 AM David Marchand wrote: > > The mentioned changes broke existing applications when the link status > of i40e ports is down at the time the port is started. > Revert those changes, the original issue will need a different fix. > > Fixes: a4ba77367923 ("net/i40e: enable maximum frame size at port level") > Fixes: 2184f7cdeeaa ("net/i40e: fix max frame size config at port level") > Fixes: 719469f13b11 ("net/i40e: fix jumbo frame Rx with X722") > Cc: stable@dpdk.org > > Signed-off-by: David Marchand This issue was reported only by our QE, but I suspect that real deployments will get affected. Please review. Thanks. -- David Marchand