netdev - Re: Network drivers with direct io memory accesses

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080514.171315.87012656.davem@davemloft.net>
Date:	Wed, 14 May 2008 17:13:15 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	greg@...ah.com
Cc:	netdev@...r.kernel.org
Subject: Re: Network drivers with direct io memory accesses

From: Greg KH <greg@...ah.com>
Date: Wed, 14 May 2008 17:10:44 -0700

> Both of these drivers are accessing memory on the devices directly,
> without using the proper kernel abstractions for it, making them usable
> only on x86-based boxes probably.
> 
> My question is, does this have to be fixed in order to get them
> accepted into the tree?

I'd say yes.

If that aspect isn't fixed I can't even build test them on my
computers.
--
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