From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id C14EBA0350; Fri, 26 Jun 2020 11:17:32 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id EEE4C1BE95; Fri, 26 Jun 2020 11:17:30 +0200 (CEST) Received: from us-smtp-delivery-1.mimecast.com (us-smtp-1.mimecast.com [205.139.110.61]) by dpdk.org (Postfix) with ESMTP id 202A31BE83 for ; Fri, 26 Jun 2020 11:17:28 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1593163048; 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=nf6doWk4Xfa6IaTlr2XoN2Nxr7YhLUkU+TIHpoGYm94=; b=Qd3DRBYrcCeQHA+olEDxSmxceep9D6p3gk36s7UAoNIyfYS0URV8b2c3kOMFTh7U73XLgV pMutlXuL2a/IWpihqspgcOSEnjNwCxa7KRIXkVHNJBzduy0OqYXGBTjQEpN0RowJqu4bPc 748u6AJFkZBTSVSGsAgSmuexK9DY/8w= Received: from mail-ua1-f70.google.com (mail-ua1-f70.google.com [209.85.222.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-102-q_-uJsjZNNG7JjsG1rg3BA-1; Fri, 26 Jun 2020 05:17:27 -0400 X-MC-Unique: q_-uJsjZNNG7JjsG1rg3BA-1 Received: by mail-ua1-f70.google.com with SMTP id h19so1421997uac.14 for ; Fri, 26 Jun 2020 02:17:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=nf6doWk4Xfa6IaTlr2XoN2Nxr7YhLUkU+TIHpoGYm94=; b=sCbkRnAXwiwUU8Q9xUwoGyPVCbN+OlA7ISc/HpWKgc/71ykDE6dmSutJnESq8aJPe0 0ZpMIvdr7J+b2ZCwZjEI/BVMKkkcwvJ0Nsfoz0JOZbSMjibhrXnxWu+TLNIDk3iM7th0 KCsONCDaDfJAzTGhgGBmusAkDvWV8J/4G57Op7ylL2GK0qm4FqPxhMb1T7RaJXQqbTpI 534Hzzw20ZCpYQrxf6DHUvDmqv8crh7r9kWPw0Q7v6aAXOsnezWhScFxCuK8rl1HYCLd NBBiqoKEB34mmu46o7Q4Ymbt+LeNIVzg2QRzK4+jm6NpHUmbzpJpp5rUzhNJU1H8gUgY /IAw== X-Gm-Message-State: AOAM531L3h5NSZSg2HAHSjtoTPVedkeEOz7obFOpSw0gPhEO5CdvdPqX +fuXDKlxSgvo7S0w9OkG+k7SqXlS3MhfAQ0PC1paE5Jq/ZjAdic19PerH4i24OyFADJ4X7Uyp8i 0bTXuLiyP2wVhzmB31CA= X-Received: by 2002:a67:2fc6:: with SMTP id v189mr1677043vsv.198.1593163046237; Fri, 26 Jun 2020 02:17:26 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxsV4R/ysY3wpEnj0DoLHzwc+7Q9DnINzw12jBNMrgnomJQEEvj7Z+16RuATcVVM66VA2REoTlJpNxIddWe7hg= X-Received: by 2002:a67:2fc6:: with SMTP id v189mr1677022vsv.198.1593163045963; Fri, 26 Jun 2020 02:17:25 -0700 (PDT) MIME-Version: 1.0 References: <20200621174035.6858-1-haiyue.wang@intel.com> <20200625035046.19820-1-haiyue.wang@intel.com> In-Reply-To: From: David Marchand Date: Fri, 26 Jun 2020 11:17:15 +0200 Message-ID: To: "Wang, Haiyue" Cc: Kevin Traynor , Luca Boccassi , dev , "Burakov, Anatoly" , dpdk stable , Harman Kalra Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dmarchan@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH v4] bus/pci: fix VF bus error for memory access X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, Jun 25, 2020 at 8:34 PM Wang, Haiyue wrote: > > > I can see that some distros have already started backporting the fix > > > in kernel (fc31, fc32 and rhel7 at least for what I saw). > > > 18.11 and 19.11 will need this fix at some point. > > > I'll let you decide on the proper timing. > > > > > > > > > > It looks an important fix. I think it's worth having in 18.11.9. I will > > apply and create an 18.11.9-rc2 tomorrow, so if anyone hasn't started > > validation already, they can validate with it in. > > Alex post a fix in kernel just now. So looks like the DPDK patch is nice > to have, not a MUST. ;-) > > https://lore.kernel.org/kvm/159310421505.27590.16617666489295503039.stgit@gimli.home/T/#u Yes, this has been discussed offlist and Alex proposed an adjustment on the CVE fix. But we still have to live with the situation where people will have only the first part of the fix. I am still for backporting this change to stable branches. -- David Marchand