public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Mayer <andrea.mayer@uniroma2.it>
To: Mark Brown <broonie@kernel.org>, Matthieu Baerts <matttbe@kernel.org>
Cc: David Miller <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Networking <netdev@vger.kernel.org>,
	Justin Iurman <justin.iurman@6wind.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Andrea Mayer <andrea.mayer@uniroma2.it>
Subject: Re: linux-next: manual merge of the net-next tree with the netfilter tree
Date: Thu, 9 Apr 2026 03:04:57 +0200	[thread overview]
Message-ID: <20260409030457.a37c01254eb615b9b410e183@uniroma2.it> (raw)
In-Reply-To: <d9d4e328-6668-4c24-bace-77a0f93bbed6@sirena.org.uk>

On Wed, 8 Apr 2026 18:00:50 +0100
Mark Brown <broonie@kernel.org> wrote:

> On Wed, Apr 08, 2026 at 06:43:36PM +0200, Matthieu Baerts wrote:
> > On 08/04/2026 17:08, Mark Brown wrote:
> 
> > > 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:
> 
> >  +	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;
> >  +		}
> >  +	}
> >  +
> 
> Yes, that's the additional fixup I mentioned above - it didn't conflict
> for me (well, the exit path did).

Thanks Mark and Matthieu for taking care of this.

I went through both commits and the rerere.
The resolution looks correct from the seg6 side. Build-tested.

Happy to help if anything else comes up.

Cheers,
Andrea

  reply	other threads:[~2026-04-09  1:05 UTC|newest]

Thread overview: 12+ 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
2026-04-08 17:00     ` Mark Brown
2026-04-09  1:04       ` Andrea Mayer [this message]
  -- 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=20260409030457.a37c01254eb615b9b410e183@uniroma2.it \
    --to=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=matttbe@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