| 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: Mon, 3 Mar 2008 11:57:52 +0100 From: Ingo Molnar <mingo@...e.hu> To: Pavel Roskin <proski@....org> Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Zan Lynx <zlynx@....org>, linux-kernel <linux-kernel@...r.kernel.org>, Jon Masters <jcm@...masters.org>, Rusty Russell <rusty@...tcorp.com.au> Subject: Re: [PATCH 2.6.25] module: allow ndiswrapper to use GPL-only symbols * Pavel Roskin <proski@....org> wrote: > > btw., what are the technical reasons why ndiswrapper cannot be done > > in userspace, much like the (wildly successful) FUSE concept? > > ndiswrapper contains essentially two drivers in one - PCI and USB. > The PCI driver uses DMA, which should be a strong argument for keeping > it in the kernel. how exactly does it use DMA - how does it allocate the memory it later on DMAs into, and how does it typically program that DMA target - is there any control over that in the NDIS protocol - or will NDIS drivers just write random addresses to the mmio space and then the hardware does DMA to/from those addresses? [without the NDIS framework having any knowledge about the encoding of those bits?] on modern hardware it might even be possible to jail an ndiswrapper driver to its own pages via the IOMMU. Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists