From: Matthieu Baerts <matttbe@kernel.org>
To: Mark Brown <broonie@kernel.org>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Networking <netdev@vger.kernel.org>
Cc: Andrea Mayer <andrea.mayer@uniroma2.it>,
Justin Iurman <justin.iurman@6wind.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the net-next tree with the netfilter tree
Date: Wed, 8 Apr 2026 18:43:36 +0200 [thread overview]
Message-ID: <8d216893-1e0b-4e3c-8609-eb3de5da02cf@kernel.org> (raw)
In-Reply-To: <729b748b-e00b-475e-81e0-a666eab24fc6@sirena.org.uk>
Hello,
On 08/04/2026 17:08, Mark Brown wrote:
> On Wed, Apr 08, 2026 at 03:10:10PM +0100, Mark Brown wrote:
>> Hi all,
>>
>> Today's linux-next merge of the net-next tree got a conflict in:
>>
>> net/ipv6/seg6_iptunnel.c
>>
>> between commit:
>>
>> c3812651b522f ("seg6: separate dst_cache for input and output paths in seg6 lwtunnel")
>>
>> from the netfilter tree and commit:
>>
>> 78723a62b969a ("seg6: add per-route tunnel source address")
>>
>> from the net-next tree.
>>
>> I fixed it up (see below) and can carry the fix as necessary. This
>> is now fixed as far as linux-next is concerned, but any non trivial
>> conflicts should be mentioned to your upstream maintainer when your tree
>> is submitted for merging. You may also want to consider cooperating
>> with the maintainer of the conflicting tree to minimise any particularly
>> complex conflicts.
Thank you for having fixed the conflict on linux-next!
>> diff --cc net/ipv6/seg6_iptunnel.c
>> index d6a0f7df90807,e76cc0cc481ec..0000000000000
>> --- a/net/ipv6/seg6_iptunnel.c
>> +++ b/net/ipv6/seg6_iptunnel.c
>> @@@ -48,8 -48,8 +48,9 @@@ static size_t seg6_lwt_headroom(struct
>> }
>>
>> struct seg6_lwt {
>> - struct dst_cache cache;
>> + struct dst_cache cache_input;
>> + struct dst_cache cache_output;
>> + struct in6_addr tunsrc;
>> struct seg6_iptunnel_encap tuninfo[];
>> };
>>
>
> This also needs a fixup for a new jump to the error handling paths that
> was added in seg6_build_state().
I also had this other conflict there, and I did this when resolving it
in MPTCP tree:
--------------------- 8< ---------------------
diff --cc net/ipv6/seg6_iptunnel.c
index e76cc0cc481e,d6a0f7df9080..97b50d9b1365
--- a/net/ipv6/seg6_iptunnel.c
+++ b/net/ipv6/seg6_iptunnel.c
@@@ -48,8 -48,8 +48,9 @@@ static size_t seg6_lwt_headroom(struct
}
struct seg6_lwt {
- struct dst_cache cache;
+ struct dst_cache cache_input;
+ struct dst_cache cache_output;
+ struct in6_addr tunsrc;
struct seg6_iptunnel_encap tuninfo[];
};
@@@ -726,18 -712,6 +731,18 @@@ static int seg6_build_state(struct net
memcpy(&slwt->tuninfo, tuninfo, tuninfo_len);
+ if (tb[SEG6_IPTUNNEL_SRC]) {
+ slwt->tunsrc = nla_get_in6_addr(tb[SEG6_IPTUNNEL_SRC]);
+
+ if (ipv6_addr_any(&slwt->tunsrc) ||
+ ipv6_addr_is_multicast(&slwt->tunsrc) ||
+ ipv6_addr_loopback(&slwt->tunsrc)) {
+ NL_SET_ERR_MSG(extack, "invalid tunsrc address");
+ err = -EINVAL;
- goto free_dst_cache;
++ goto err_destroy_output;
+ }
+ }
+
newts->type = LWTUNNEL_ENCAP_SEG6;
newts->flags |= LWTUNNEL_STATE_INPUT_REDIRECT;
@@@ -750,9 -724,9 +755,11 @@@
return 0;
- free_dst_cache:
- dst_cache_destroy(&slwt->cache);
- free_lwt_state:
++err_destroy_output:
++ dst_cache_destroy(&slwt->cache_output);
+ err_destroy_input:
+ dst_cache_destroy(&slwt->cache_input);
+ err_free_newts:
kfree(newts);
return err;
}
--------------------- 8< ---------------------
I took the liberty to add the err_destroy_output label, similar to the
new err_destroy_input one.
Just in case, rerere cache file is available there:
https://github.com/multipath-tcp/mptcp-upstream-rr-cache/commit/dbb6675
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-04-08 16:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 14:10 linux-next: manual merge of the net-next tree with the netfilter tree Mark Brown
2026-04-08 15:08 ` Mark Brown
2026-04-08 16:43 ` Matthieu Baerts [this message]
2026-04-08 17:00 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2020-12-10 2:11 Stephen Rothwell
2018-08-07 2:49 Stephen Rothwell
2018-08-15 23:47 ` Stephen Rothwell
2018-08-16 0:08 ` Pablo Neira Ayuso
2016-11-09 23:56 Stephen Rothwell
2016-11-10 0:31 ` Pablo Neira Ayuso
2016-11-13 4:43 ` David Miller
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=8d216893-1e0b-4e3c-8609-eb3de5da02cf@kernel.org \
--to=matttbe@kernel.org \
--cc=andrea.mayer@uniroma2.it \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=justin.iurman@6wind.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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