Re: [PATCH 0/2] swiotlb: rework fix info leak with DMA_FROM_DEVICE

2022-03-04 Thread Matthew Wilcox
On Fri, Mar 04, 2022 at 05:29:08PM +0100, Halil Pasic wrote: > No problem, I can do that. It isn't hard to squash things together, but > when I was about to write the commit message, I had the feeling doing > a revert is cleaner. > > Any other opinions? One patch, not two. ___

Re: [PATCH 0/2] swiotlb: rework fix info leak with DMA_FROM_DEVICE

2022-03-04 Thread Halil Pasic
On Fri, 4 Mar 2022 07:53:48 -0800 Christoph Hellwig wrote: > On Fri, Mar 04, 2022 at 02:58:57PM +0100, Halil Pasic wrote: > > Unfortunately, we ended up with the wrong version of the patch "fix info > > leak with DMA_FROM_DEVICE" getting merged. We got v4 merged, but the > > version we want is v7

Re: [PATCH 0/2] swiotlb: rework fix info leak with DMA_FROM_DEVICE

2022-03-04 Thread Christoph Hellwig
On Fri, Mar 04, 2022 at 02:58:57PM +0100, Halil Pasic wrote: > Unfortunately, we ended up with the wrong version of the patch "fix info > leak with DMA_FROM_DEVICE" getting merged. We got v4 merged, but the > version we want is v7 with some minor tweaks which were supposed to be > applied by Christ

[PATCH 0/2] swiotlb: rework fix info leak with DMA_FROM_DEVICE

2022-03-04 Thread Halil Pasic
Unfortunately, we ended up with the wrong version of the patch "fix info leak with DMA_FROM_DEVICE" getting merged. We got v4 merged, but the version we want is v7 with some minor tweaks which were supposed to be applied by Christoph (swiotlb maintainer). After pointing this out, I was asked by Chr