| 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: <20070909061551G.tomof@acm.org> Date: Mon, 10 Sep 2007 00:05:20 +0900 From: FUJITA Tomonori <tomof@....org> To: hch@...radead.org Cc: jeff@...zik.org, tomof@....org, open-iscsi@...glegroups.com, davem@...emloft.net, mchristi@...hat.com, netdev@...r.kernel.org, anilgv@...adcom.com, talm@...adcom.com, lusinsky@...adcom.com, uri@...adcom.com, fujita.tomonori@....ntt.co.jp Subject: Re: [PATCH v3 2/2][BNX2]: Add iSCSI support to BNX2 devices. On Sat, 8 Sep 2007 13:00:36 +0100 Christoph Hellwig <hch@...radead.org> wrote: > On Sat, Sep 08, 2007 at 07:32:27AM -0400, Jeff Garzik wrote: > > FUJITA Tomonori wrote: > > >Yeah, iommu code ignores the lld limitations (the problem is that the > > >lld limitations are in request_queue and iommu code can't access to > > >request_queue). There is no way to tell iommu code about the lld > > >limitations. > > > > > > This fact very much wants fixing. > > > Absolutely. Unfortunately everyone wastes their time on creating workarounds > instead of fixing the underlying problem. Any ideas on how to fix this? I chatted to Jens and James on this last week. - we could just copies the lld limitations to device structure. it's hacky but device structure already has hacky stuff. - we could just link device structure to request_queue structure so that iommu code can see request_queue structure. - we could remove the lld limitations in request_queue strucutre and have a new strucutre (something like struct io_restrictions). then somehow we could link the new structure with request_queue and device strucutres. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists