netdev - Re: [RFC:] struct net_device_ops: Add function pointer to fill device specific ndisc information

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]

Date:	Mon, 21 Jan 2013 09:28:06 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	stephan.gatzka@...il.com
Cc:	"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>,
	linux1394-devel@...ts.sourceforge.net, netdev@...r.kernel.org,
	yoshfuji@...ux-ipv6.org, davem@...emloft.net
Subject: Re: [RFC:] struct net_device_ops: Add function pointer to fill
 device specific ndisc information

On Jan 21 Stephan Gatzka wrote:
> On Jan 20 Waskiewicz Jr, Peter P wrote:
> > I'm no expert on firewire requirements, but if you go down the path
> > of adding a net_device_ops member, I'd recommend adding a pointer
> > to your own struct of ops.  This would be similar to wireless ops.
> >
> > Only a suggestion, since you may still need to add more ops later
> > on, and this way you can contain the inflation to a firewire-specific
> > struct of function pointers.
> >
> 
> Thanks for your note. Right now I only need on function pointer for 
> filling RFC3146 information and I can imagine doing the same for 
> IPv4/ARP which would be a second function.

There is a limited count of IEEE 1394 specifics:

  a) RFC 2734 ARP:  currently implemented by inspecting and mangling ARP
     packets within the firewire-net driver (inbound as well as outbound
     packets).

  b) RFC 2734 MCAP (Multicast Channel Allocation Protocol):  currently not
     implemented; not sure if needed (I see a few big downsides to using
     per-multicast-group channels); not sure if networking core support
     would be needed for this

  c) RFC 2855 DHCP for IEEE 1394:  currently not implemented; not sure if
     needed; not sure if it would concern the kernel at all

  d) RFC 3146 NDISC (Neighbor Discovery Protocol for IPv6):  That's the
     only real problem in search of a solution.

I bet there won't be any additional RFCs invented for networking over
1394, ever.
-- 
Stefan Richter
-=====-===-= ---= =-=-=
http://arcgraph.de/sr/
--
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