lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <5aaca0d3-417f-57f3-969f-b4c777c3fd48@kernel.dk> Date: Tue, 24 Apr 2018 20:02:56 -0600 From: Jens Axboe <axboe@...nel.dk> To: Christoph Hellwig <hch@....de>, iommu@...ts.linux-foundation.org, linux-arch@...r.kernel.org, linux-block@...r.kernel.org, linux-ide@...r.kernel.org, linux-scsi@...r.kernel.org, netdev@...r.kernel.org Cc: "David S. Miller" <davem@...emloft.net>, linux-kernel@...r.kernel.org Subject: Re: [PATCH 2/5] ide: kill ide_toggle_bounce On 4/24/18 12:16 PM, Christoph Hellwig wrote: > ide_toggle_bounce did select various strange block bounce limits, including > not bouncing at all as soon as an iommu is present in the system. Given > that the dma_map routines now handle any required bounce buffering except > for ISA DMA, and the ide code already must handle either ISA DMA or highmem > at least for iommu equipped systems we can get rid of the block layer > bounce limit setting entirely. Pretty sure I was the one to add this code, when highmem page IO was enabled about two decades ago... Outside of DMA, the issue was that the PIO code could not handle highmem. That's not the case anymore, so this should be fine. Reviewed-by: Jens Axboe <axboe@...nel.dk> -- Jens Axboe
Powered by blists - more mailing lists