LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Will Deacon <will@kernel.org>, iommu@lists.linux-foundation.org
Cc: linux-kernel@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
Claire Chang <tientzu@chromium.org>,
Christoph Hellwig <hch@lst.de>,
Robin Murphy <robin.murphy@arm.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Nathan Chancellor <nathan@kernel.org>,
Halil Pasic <pasic@linux.ibm.com>
Subject: Re: [PATCH v2 0/4] Fix restricted DMA vs swiotlb_exit()
Date: Thu, 22 Jul 2021 21:22:58 +0200 [thread overview]
Message-ID: <57e37ef9-c055-d6a6-2244-2c7dd243b5c1@de.ibm.com> (raw)
In-Reply-To: <20210720133826.9075-1-will@kernel.org>
On 20.07.21 15:38, Will Deacon wrote:
> Hi again, folks,
>
> This is version two of the patch series I posted yesterday:
>
> https://lore.kernel.org/r/20210719123054.6844-1-will@kernel.org
>
> The only changes since v1 are:
>
> * Squash patches 2 and 3, amending the commit message accordingly
> * Add Reviewed-by and Tested-by tags from Christoph and Claire (thanks!)
>
> I'd usually leave it a bit longer between postings, but since this fixes
> issues with patches in -next I thought I'd spin a new version immediately.
>
> Cheers,
FWIW, I just bisected virtio-errors with secure execution mode
qemu-system-s390x: virtio-serial-bus: Unexpected port id 4205794771 for device virtio-serial0.0
to
commit 903cd0f315fe426c6a64c54ed389de0becb663dc
Author: Claire Chang <tientzu@chromium.org>
Date: Thu Jun 24 23:55:20 2021 +0800
swiotlb: Use is_swiotlb_force_bounce for swiotlb data bouncing
Unfortunately this patch series does NOT fix this issue, so it seems that even more
things are broken.
Any idea what else might be broken?
Shall we rather revert these patches from next until we have things under control?
next prev parent reply other threads:[~2021-07-22 19:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 13:38 Will Deacon
2021-07-20 13:38 ` [PATCH v2 1/4] of: Return success from of_dma_set_restricted_buffer() when !OF_ADDRESS Will Deacon
2021-07-20 13:38 ` [PATCH v2 2/4] swiotlb: Convert io_default_tlb_mem to static allocation Will Deacon
2021-07-20 13:38 ` [PATCH v2 3/4] swiotlb: Emit diagnostic in swiotlb_exit() Will Deacon
2021-07-20 13:38 ` [PATCH v2 4/4] swiotlb: Free tbl memory " Will Deacon
2021-07-31 18:26 ` Guenter Roeck
2021-08-01 2:29 ` Konrad Rzeszutek Wilk
2021-08-01 4:26 ` Guenter Roeck
2021-07-22 19:22 ` Christian Borntraeger [this message]
2021-07-23 1:12 ` [PATCH v2 0/4] Fix restricted DMA vs swiotlb_exit() Halil Pasic
2021-07-23 5:51 ` Christian Borntraeger
2021-07-23 6:14 ` Christian Borntraeger
2021-07-23 8:47 ` Halil Pasic
2021-07-23 8:50 ` Christian Borntraeger
2021-07-23 14:01 ` Konrad Rzeszutek Wilk
2021-07-23 17:53 ` Christian Borntraeger
2021-07-23 22:18 ` Halil Pasic
2021-07-24 0:29 ` Konrad Rzeszutek Wilk
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=57e37ef9-c055-d6a6-2244-2c7dd243b5c1@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nathan@kernel.org \
--cc=pasic@linux.ibm.com \
--cc=robin.murphy@arm.com \
--cc=tientzu@chromium.org \
--cc=will@kernel.org \
--subject='Re: [PATCH v2 0/4] Fix restricted DMA vs swiotlb_exit()' \
/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
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).