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] [day] [month] [year] [list]

Date:	Tue, 20 May 2008 11:33:45 -0700
From:	Greg KH <greg@...ah.com>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org
Subject: Re: Network drivers with direct io memory accesses

On Wed, May 14, 2008 at 05:28:24PM -0700, Greg KH wrote:
> On Wed, May 14, 2008 at 05:13:15PM -0700, David Miller wrote:
> > 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.
> 
> {sigh}
> 
> I figured that, but thought it would be worth it to at least ask. :)
> 
> > If that aspect isn't fixed I can't even build test them on my
> > computers.
> 
> Hm, why?  They should still build I would think, just not run properly,
> right?
> 
> Damm, I really gotta get that cross-build system set up here, I'll go
> start that right now...

Ok, I did this, and I don't see any build errors or warnings on sparc64.
Maybe the code isn't as bad as I imagined, I'll go through it all and
submit it for review.

thanks,

greg k-h
--
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