Date: Tue, 6 Jan 2015 13:52:29 -0700 From: John Nielsen <lists@jnielsen.net> To: Bryan Venteicher <bryanv@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r272886 - in head/sys: netinet netinet6 Message-ID: <C9D67F11-E922-477E-A9D6-7D2B8A139865@jnielsen.net> In-Reply-To: <201410100609.s9A690NU067686@svn.freebsd.org> References: <201410100609.s9A690NU067686@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Bryan- On Oct 10, 2014, at 12:09 AM, Bryan Venteicher <bryanv@freebsd.org> = wrote: > Author: bryanv > Date: Fri Oct 10 06:08:59 2014 > New Revision: 272886 > URL: https://svnweb.freebsd.org/changeset/base/272886 >=20 > Log: > Add context pointer and source address to the UDP tunnel callback >=20 > These are needed for the forthcoming vxlan implementation. The = context > pointer means we do not have to use a spare pointer field in the = inpcb, > and the source address is required to populate vxlan's forwarding = table. >=20 > While I highly doubt there is an out of tree consumer of the UDP > tunneling callback, this change may be a difficult to eventually MFC. I noticed this comment while doing an MFC of vxlan to my local tree. Do = you think an MFC to 10-STABLE of this change (and vxlan generally) will = be feasible? Is there precedent for ABI changes like this being = sanctioned? Could symbol versioning help? > Phabricator: https://reviews.freebsd.org/D383 > Reviewed by: gnn >=20 > Modified: > head/sys/netinet/sctputil.c > head/sys/netinet/udp_usrreq.c > head/sys/netinet/udp_var.h > head/sys/netinet6/udp6_usrreq.c Thanks, JN
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C9D67F11-E922-477E-A9D6-7D2B8A139865>