[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 2/3] public/io/netif.h: document control ring and toeplitz hashing



> > You've put the consumer values into the shared page. I'd rather not have
> > to scrutinize your shared ring implementation for other security bugs.
> > Similarly, if there's another security issues like XSA-155 I'd rather
> > not have to look at another non-standard shared ring implementation.
> 
> Ok. That's a good enough reason. I'll come up with a new prototype.

Could I suggest that you make this a more generic one? That is not
just limited to network out of band - but other drivers could 
use it as well.


> 
> > 
> > IMO, it's you who should be presenting compelling reasons for /not/
> > using the standard infrastructure, not the other way around.
> > 
> 
> There is no 'standard' here though. There's convention, but that's a 
> different thing. If we're going to have a 'no more variable size message 
> protocols' policy than that needs writing down somewhere.
> 
>   Paul
> 
> > David
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.