stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Sasha Levin <sashal@kernel.org>, Max Gurtovoy <maxg@mellanox.com>,
	mst@redhat.com
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] vdpasim: protect concurrent access to iommu iotlb
Date: Thu, 6 Aug 2020 11:41:24 +0800	[thread overview]
Message-ID: <3e73eddd-5c74-dbc7-a77b-05e1ed078c92@redhat.com> (raw)
In-Reply-To: <20200806012410.8C84322CF7@mail.kernel.org>


On 2020/8/6 上午9:24, Sasha Levin wrote:
> Hi
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag
> fixing commit: .
>
> The bot has tested the following trees: v5.7.11, v5.4.54, v4.19.135, v4.14.190, v4.9.231, v4.4.231.
>
> v5.7.11: Build OK!
> v5.4.54: Failed to apply! Possible dependencies:
>      2c53d0f64c06 ("vdpasim: vDPA device simulator")
>      961e9c84077f ("vDPA: introduce vDPA bus")
>
> v4.19.135: Failed to apply! Possible dependencies:
>      2c53d0f64c06 ("vdpasim: vDPA device simulator")
>      961e9c84077f ("vDPA: introduce vDPA bus")
>
> v4.14.190: Failed to apply! Possible dependencies:
>      2c53d0f64c06 ("vdpasim: vDPA device simulator")
>      7b95fec6d2ff ("virtio: make VIRTIO a menuconfig to ease disabling it all")
>      961e9c84077f ("vDPA: introduce vDPA bus")
>
> v4.9.231: Failed to apply! Possible dependencies:
>      0d7f4f0594fc ("MAINTAINERS: update rmk's entries")
>      2c53d0f64c06 ("vdpasim: vDPA device simulator")
>      384fe7a4d732 ("drivers: net: xgene-v2: Add DMA descriptor")
>      3b3f9a75d931 ("drivers: net: xgene-v2: Add base driver")
>      404a5c392dcc ("MAINTAINERS: fix virtio file pattern")
>      51c5d8447bd7 ("MMC: meson: initial support for GX platforms")
>      6bc37fac30cf ("arm64: dts: add Allwinner A64 SoC .dtsi")
>      70dbd9b258d5 ("MAINTAINERS: Add entry for APM X-Gene SoC Ethernet (v2) driver")
>      7683e9e52925 ("Properly alphabetize MAINTAINERS file")
>      81ccd0cab29b ("drivers: net: xgene-v2: Add mac configuration")
>      872d1ba47bdc ("MAINTAINERS: Add Actions Semi Owl section")
>      87c586a6a0e1 ("MAINTAINERS: Update the Allwinner sunXi entry")
>      961e9c84077f ("vDPA: introduce vDPA bus")
>      b105bcdaaa0e ("drivers: net: xgene-v2: Add transmit and receive")
>      b26bff6e52d8 ("MAINTAINERS: Add device tree bindings to mv88e6xx section")
>      c0a6a5ae6b5d ("MAINTAINERS: copy virtio on balloon_compaction.c")
>      d5d4602e0405 ("Staging: iio: fix a MAINTAINERS entry")
>      dbaf0624ffa5 ("crypto: add virtio-crypto driver")
>      fd33f3eca6bf ("MAINTAINERS: Add maintainers for the meson clock driver")
>
> v4.4.231: Failed to apply! Possible dependencies:
>      02038fd6645a ("crypto: Added Chelsio Menu to the Kconfig file")
>      06a8fc78367d ("VSOCK: Introduce virtio_vsock_common.ko")
>      2c53d0f64c06 ("vdpasim: vDPA device simulator")
>      404a5c392dcc ("MAINTAINERS: fix virtio file pattern")
>      433cd2c617bf ("crypto: rockchip - add crypto driver for rk3288")
>      6f99612e2500 ("tpm: Proxy driver for supporting multiple emulated TPMs")
>      961e9c84077f ("vDPA: introduce vDPA bus")
>      c0a6a5ae6b5d ("MAINTAINERS: copy virtio on balloon_compaction.c")
>      dbaf0624ffa5 ("crypto: add virtio-crypto driver")
>
>
> NOTE: The patch will not be queued to stable trees until it is upstream.
>
> How should we proceed with this patch?


The patch tries to fix a bug which is a commit introduced in 5.4.

So I think backporting it to 5.4 stable should be sufficient.

Thanks


>


  reply	other threads:[~2020-08-06  3:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-31  7:38 [PATCH] vdpasim: protect concurrent access to iommu iotlb Jason Wang
2020-08-01 23:18 ` Sasha Levin
2020-08-06  1:24 ` Sasha Levin
2020-08-06  3:41   ` Jason Wang [this message]
2020-08-13 16:25 ` Sasha Levin
2020-08-14  5:33   ` Michael S. Tsirkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3e73eddd-5c74-dbc7-a77b-05e1ed078c92@redhat.com \
    --to=jasowang@redhat.com \
    --cc=maxg@mellanox.com \
    --cc=mst@redhat.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).