From: Kai Lueke <kailueke@linux.microsoft.com>
To: stable@vger.kernel.org
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
Paul Chaignon <paul@cilium.io>,
Eyal Birger <eyal.birger@gmail.com>
Subject: Re: [PATCH] Revert "xfrm: state and policy should fail if XFRMA_IF_ID 0"
Date: Mon, 14 Mar 2022 13:19:19 +0100 [thread overview]
Message-ID: <076e8c72-b842-64a8-7a4b-9a3b30715b5d@linux.microsoft.com> (raw)
In-Reply-To: <20220307082245.GA1791239@gauss3.secunet.de>
I forgot to CC stable@ when submitting, doing it now:
Can this be picked for the next round of stable kernels (down to 5.10)?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a3d9001b4e287fc043e5539d03d71a32ab114bcb
Thanks,
Kai
On 07.03.2022 09:22, Steffen Klassert wrote:
> On Thu, Mar 03, 2022 at 03:55:10PM +0100, kailueke@linux.microsoft.com wrote:
>> From: Kai Lueke <kailueke@linux.microsoft.com>
>>
>> This reverts commit 68ac0f3810e76a853b5f7b90601a05c3048b8b54 because ID
>> 0 was meant to be used for configuring the policy/state without
>> matching for a specific interface (e.g., Cilium is affected, see
>> https://github.com/cilium/cilium/pull/18789 and
>> https://github.com/cilium/cilium/pull/19019).
>>
>> Signed-off-by: Kai Lueke <kailueke@linux.microsoft.com>
> Applied, thanks Kai!
next parent reply other threads:[~2022-03-14 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220303145510.324-1-kailueke@linux.microsoft.com>
[not found] ` <20220307082245.GA1791239@gauss3.secunet.de>
2022-03-14 12:19 ` Kai Lueke [this message]
2022-03-14 12:27 ` [PATCH] Revert "xfrm: state and policy should fail if XFRMA_IF_ID 0" Greg KH
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=076e8c72-b842-64a8-7a4b-9a3b30715b5d@linux.microsoft.com \
--to=kailueke@linux.microsoft.com \
--cc=eyal.birger@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul@cilium.io \
--cc=stable@vger.kernel.org \
--cc=steffen.klassert@secunet.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).