netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: tparkin@katalix.com
Cc: netdev@vger.kernel.org, jchapman@katalix.com, celston@katalix.com
Subject: Re: [PATCH 0/2] l2tp: fix ancilliary data handling in ip6 recv
Date: Tue, 29 Jan 2013 14:12:39 -0500 (EST)	[thread overview]
Message-ID: <20130129.141239.2228875361542418234.davem@davemloft.net> (raw)
In-Reply-To: <1359370134-29875-1-git-send-email-tparkin@katalix.com>

From: Tom Parkin <tparkin@katalix.com>
Date: Mon, 28 Jan 2013 10:48:52 +0000

> l2tp_ip6 was using the IPv4 handler functions for ancilliary data, which meant
> that socket options such as e.g. IPV6_RECVPKTINFO are not correctly passed to
> userspace.
> 
> This patchset:
> 
> 	*  exports the IPv6 recv handler function datagram_recv_ctl so that
> 	   modules may access it
> 	*  updates l2tp_ip6 to use datagram_recv_ctl rather than ip_cmsg_recv

What a mess.

Well, no surprise that usage of these routines is often wrong given
the non-descript names the functions have.

Please rewrite this patch set, starting with a rename of both
datagram_recv_ctl() and datagram_send_ctl() such that you can
tell, by name, that they are ipv6 specific functions.

Please make sure to grep the entire tree and fix up all references,
they are references to the names in comments too.

They currently look like generic routines that might be found in
net/core/datagram.c and might be usable for all protocols, but that's
definitely not the case.

They are ipv6 specific, and if they are exported globally they must
have something expressing their ipv6'ness in their names.

Thanks.

  parent reply	other threads:[~2013-01-29 19:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28 10:48 [PATCH 0/2] l2tp: fix ancilliary data handling in ip6 recv Tom Parkin
2013-01-28 10:48 ` [PATCH 1/2] ipv6: export symbol datagram_recv_ctl in datagram.c Tom Parkin
2013-01-28 10:48 ` [PATCH 2/2] l2tp: correctly handle ancilliary data for ip6 recv Tom Parkin
2013-01-29 19:12 ` David Miller [this message]
2013-01-30  9:50   ` [PATCH 0/2] l2tp: fix ancilliary data handling in " Tom Parkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130129.141239.2228875361542418234.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=celston@katalix.com \
    --cc=jchapman@katalix.com \
    --cc=netdev@vger.kernel.org \
    --cc=tparkin@katalix.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).