[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=whScWZnR_DZ12grwOcH_WnU1hJ_YXFmU5GNqrBkhiKgPQ@mail.gmail.com>
Date: Sun, 27 Mar 2022 17:37:24 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Halil Pasic <pasic@...ux.ibm.com>
Cc: Toke Høiland-Jørgensen <toke@...e.dk>,
Robin Murphy <robin.murphy@....com>,
Christoph Hellwig <hch@....de>,
Maxime Bizon <mbizon@...ebox.fr>,
Oleksandr Natalenko <oleksandr@...alenko.name>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Kalle Valo <kvalo@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Olha Cherevyk <olha.cherevyk@...il.com>,
iommu <iommu@...ts.linux-foundation.org>,
linux-wireless <linux-wireless@...r.kernel.org>,
Netdev <netdev@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
stable <stable@...r.kernel.org>
Subject: Re: [REGRESSION] Recent swiotlb DMA_FROM_DEVICE fixes break
ath9k-based AP
On Sun, Mar 27, 2022 at 4:37 PM Halil Pasic <pasic@...ux.ibm.com> wrote:
>
>
> For the record, I believe that the partial revert proposed here
> https://www.spinics.net/lists/linux-wireless/msg222300.html
> would have been a wiser choice, than a complete revert of commit
> aa6f8dcbab47 ("swiotlb: rework "fix info leak with DMA_FROM_DEVICE"").
Yeah, the revert is basically my standard "this doesn't work,
discussion is still ongoing" thing.
I agree that the revert then brought back that DMA_ATTR_SKIP_CPU_SYNC
complexity.
So that part of commit aa6f8dcbab47 was probably all good.
I somehow missed that Oleksandr had a tested-by for that smaller change too.
Linus
Powered by blists - more mailing lists