netdev - skb_bond: Let master see skb

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

Date:	Thu, 3 Jul 2008 05:21:29 -0700 (PDT)
From:	Doug Kehn <rdkehn@...oo.com>
To:	netdev@...r.kernel.org
Subject: skb_bond: Let master see skb

Hi All,

I was looking at writing a net driver for a Marvell switch chip attached 
to an Ethernet MAC on a SoC.  The driver would be similar to the bonding 
driver except that it would bond to a single slave (the SoC Ethernet 
driver) and export multiple net devs.  The idea is to steer frames to a physical port on the switch by adding a 4-byte trailer to the frame.  The 
switch will use the trailer to determine the port to send the frame.  The switch also strips the trailer before sending.  On packet reception, the 
switch adds the 4-byte trailer to the frame indicating the physical port 
the frame was received.  The master needs to see the skb in order to determine the actual dev to associate with the skb and to strip off the 
4-byte trailer.

I was thinking of adding a function pointer to net_dev to allow a master 
to see the skb and have skb_bond() call the function if the pointer has 
been initialized.  skb_bond would function as is if the pointer is not 
initialized.

Is there a better way to accomplish this or is this approach reasonable?

Thanks,
...doug

--
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