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
| ||
|
Date: Thu, 24 Jan 2019 09:42:21 +0100 From: Christoph Hellwig <hch@....de> To: Joerg Roedel <joro@...tes.org> Cc: Christoph Hellwig <hch@....de>, "Michael S . Tsirkin" <mst@...hat.com>, Jason Wang <jasowang@...hat.com>, Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>, Jens Axboe <axboe@...nel.dk>, virtualization@...ts.linux-foundation.org, linux-block@...r.kernel.org, linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org, jfehlig@...e.com, jon.grimm@....com, brijesh.singh@....com, jroedel@...e.de Subject: Re: [PATCH 5/5] virtio-blk: Consider virtio_max_dma_size() for maximum segment size On Thu, Jan 24, 2019 at 09:40:11AM +0100, Joerg Roedel wrote: > > I wonder if we should just move the dma max segment size check > > into blk_queue_max_segment_size so that all block drivers benefit > > from it. Even if not I think at least the SCSI midlayer should > > be updated to support it. > > In that case the limit would also apply to virtio-blk even if it doesn't > use the DMA-API. If that is acceptable we can move the check to > blk_queue_max_segment_size(). Yes. But more importantly it would fix the limit for all other block drivers that set large segment sizes when running over swiotlb.
Powered by blists - more mailing lists