Re: [PATCH v2 1/1] swiotlb: rework "fix info leak with DMA_FROM_DEVICE"

2022-03-06 Thread Christoph Hellwig
On Sun, Mar 06, 2022 at 12:30:55PM -0800, Linus Torvalds wrote: > So I would expect that > > (a) READ/WRITE actually fills the whole buffer > > (b) READ/WRITE are the only ones where we care about performance at a > bounce-buffer level > > so it boils down to "do we still do this horrible memc

Re: [PATCH v2 1/1] swiotlb: rework "fix info leak with DMA_FROM_DEVICE"

2022-03-06 Thread Linus Torvalds
On Sat, Mar 5, 2022 at 11:58 PM Christoph Hellwig wrote: > > All of thee apply to all I/O. SG_IO is just a vector here as a > particularly badly designed userspace interface that happens to get a > decent test coverage. I phrased that badly. I didn't mean SG_IO in particular, I meant any of the

Re: [PATCH v2 1/1] swiotlb: rework "fix info leak with DMA_FROM_DEVICE"

2022-03-05 Thread Christoph Hellwig
On Sat, Mar 05, 2022 at 11:44:51AM -0800, Linus Torvalds wrote: > Christoph, I am assuming I'll get this from you, but if you have > nothing else pending, just holler and I can take it directly. I have nothing else pending, so feel free to take it directly: Reviewed-by: Christoph Hellwig > That

Re: [PATCH v2 1/1] swiotlb: rework "fix info leak with DMA_FROM_DEVICE"

2022-03-05 Thread Linus Torvalds
On Sat, Mar 5, 2022 at 9:07 AM Halil Pasic wrote: > > Unfortunately, we ended up merging an old version of the patch "fix info > leak with DMA_FROM_DEVICE" instead of merging the latest one. Christoph > (the swiotlb maintainer), he asked me to create an incremental fix > (after I have pointed this

[PATCH v2 1/1] swiotlb: rework "fix info leak with DMA_FROM_DEVICE"

2022-03-05 Thread Halil Pasic
Unfortunately, we ended up merging an old version of the patch "fix info leak with DMA_FROM_DEVICE" instead of merging the latest one. Christoph (the swiotlb maintainer), he asked me to create an incremental fix (after I have pointed this out the mix up, and asked him for guidance). So here we go.