All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: "David S . Miller" <davem@davemloft.net>,
	Paolo Abeni <pabeni@redhat.com>,
	Eric Dumazet <edumazet@google.com>,
	David Ahern <dsahern@kernel.org>,
	netdev@vger.kernel.org
Subject: Re: [PATCH net 0/4] vrf: fix source address selection with route leak
Date: Mon, 24 Jun 2024 13:30:39 -0700	[thread overview]
Message-ID: <20240624133039.5b0eb17c@kernel.org> (raw)
In-Reply-To: <20240624130859.953608-1-nicolas.dichtel@6wind.com>

On Mon, 24 Jun 2024 15:07:52 +0200 Nicolas Dichtel wrote:
> For patch 1 and 2, I didn't find the exact commit that introduced this bug, but
> I suspect it has been here since the first version. I arbitrarily choose one.

I think this breaks fcnal:

https://netdev-3.bots.linux.dev/vmksft-net/results/654201/1-fcnal-test-sh/stdout
-- 
pw-bot: cr

  parent reply	other threads:[~2024-06-24 20:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-24 13:07 [PATCH net 0/4] vrf: fix source address selection with route leak Nicolas Dichtel
2024-06-24 13:07 ` [PATCH net 1/4] ipv4: " Nicolas Dichtel
2024-06-24 13:07 ` [PATCH net 2/4] ipv6: " Nicolas Dichtel
2024-06-24 13:07 ` [PATCH net 3/4] ipv6: take care of scope when choosing the src addr Nicolas Dichtel
2024-06-24 13:07 ` [PATCH net 4/4] selftests: vrf_route_leaking: add local ping test Nicolas Dichtel
2024-06-27 10:57   ` Simon Horman
2024-07-05 13:34     ` Nicolas Dichtel
2024-06-24 20:30 ` Jakub Kicinski [this message]
2024-06-24 21:37   ` [PATCH net 0/4] vrf: fix source address selection with route leak Nicolas Dichtel

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=20240624133039.5b0eb17c@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.