From: David Ahern <dsahern@gmail.com>
To: Justin Iurman <justin.iurman@uliege.be>, netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, yoshfuji@linux-ipv6.org,
dsahern@kernel.org
Subject: Re: [PATCH net-next 1/2] ipv6: ioam: Add support for the ip6ip6 encapsulation
Date: Wed, 29 Sep 2021 21:26:23 -0600 [thread overview]
Message-ID: <16630ce5-4c61-a16b-8125-8ec697d6c33e@gmail.com> (raw)
In-Reply-To: <20210928190328.24097-2-justin.iurman@uliege.be>
On 9/28/21 1:03 PM, Justin Iurman wrote:
> @@ -42,34 +49,15 @@ static struct ioam6_lwt_encap *ioam6_lwt_info(struct lwtunnel_state *lwt)
> return &ioam6_lwt_state(lwt)->tuninfo;
> }
>
> -static struct ioam6_trace_hdr *ioam6_trace(struct lwtunnel_state *lwt)
> +static struct ioam6_trace_hdr *ioam6_lwt_trace(struct lwtunnel_state *lwt)
> {
> return &(ioam6_lwt_state(lwt)->tuninfo.traceh);
> }
>
> static const struct nla_policy ioam6_iptunnel_policy[IOAM6_IPTUNNEL_MAX + 1] = {
> - [IOAM6_IPTUNNEL_TRACE] = NLA_POLICY_EXACT_LEN(sizeof(struct ioam6_trace_hdr)),
> + [IOAM6_IPTUNNEL_TRACE] = NLA_POLICY_EXACT_LEN(sizeof(struct ioam6_iptunnel_trace)),
you can't do that. Once a kernel is released with a given UAPI, it can
not be changed. You could go the other way and handle
struct ioam6_iptunnel_trace {
+ struct ioam6_trace_hdr trace;
+ __u8 mode;
+ struct in6_addr tundst; /* unused for inline mode */
+};
Also, no gaps in uapi. Make sure all holes are stated; an anonymous
entry is best.
> };
>
> -static int nla_put_ioam6_trace(struct sk_buff *skb, int attrtype,
> - struct ioam6_trace_hdr *trace)
> -{
> - struct ioam6_trace_hdr *data;
> - struct nlattr *nla;
> - int len;
> -
> - len = sizeof(*trace);
> -
> - nla = nla_reserve(skb, attrtype, len);
> - if (!nla)
> - return -EMSGSIZE;
> -
> - data = nla_data(nla);
> - memcpy(data, trace, len);
> -
> - return 0;
> -}
> -
quite a bit of the change seems like refactoring from existing feature
to allow the new ones. Please submit refactoring changes as a
prerequisite patch. The patch that introduces your new feature should be
focused solely on what is needed to implement that feature.
next prev parent reply other threads:[~2021-09-30 3:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 19:03 [PATCH net-next 0/2] Support for the ip6ip6 encapsulation of IOAM Justin Iurman
2021-09-28 19:03 ` [PATCH net-next 1/2] ipv6: ioam: Add support for the ip6ip6 encapsulation Justin Iurman
2021-09-30 3:26 ` David Ahern [this message]
2021-09-30 15:19 ` Justin Iurman
2021-09-30 18:20 ` David Ahern
2021-10-01 11:38 ` Justin Iurman
2021-10-01 14:06 ` David Ahern
2021-10-01 14:10 ` Justin Iurman
2021-09-28 19:03 ` [PATCH net-next 2/2] selftests: net: Test for the IOAM encapsulation with IPv6 Justin Iurman
2021-09-30 3:20 ` [PATCH net-next 0/2] Support for the ip6ip6 encapsulation of IOAM David Ahern
2021-09-30 12:32 ` Justin Iurman
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=16630ce5-4c61-a16b-8125-8ec697d6c33e@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=justin.iurman@uliege.be \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/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).