From: "Kai Lüke" <kailueke@linux.microsoft.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org,
Steffen Klassert <steffen.klassert@secunet.com>,
Eyal Birger <eyal.birger@gmail.com>
Subject: Re: [PATCH 2/2] Revert "xfrm: state and policy should fail if XFRMA_IF_ID 0"
Date: Tue, 1 Mar 2022 14:12:41 +0100 [thread overview]
Message-ID: <0d449d5b-e169-cd9f-0731-9a45b25da3cb@linux.microsoft.com> (raw)
In-Reply-To: <20220228224332.0cca8d99@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
Hello,
> What's the story here? You posted your patches twice and they look
> white space damaged (tabs replaced by spaces).
yeah, sorry for the spam, now I've set up git send-email and hope it
works ;)
> Does commit 6d0d95a1c2b0
> ("xfrm: fix the if_id check in changelink") which is in net/master now
> solve the issue for you?
I don't think it solves the regression that the kernel now fails
syscalls that use id 0. I reported this to the LTS kernel list and was
told to send it here since it is a regression.
Regards,
Kai
next prev parent reply other threads:[~2022-03-01 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 18:51 [PATCH 1/2] Revert "xfrm: interface with if_id 0 should return error" Kai Lüke
2022-02-28 18:53 ` [PATCH 2/2] Revert "xfrm: state and policy should fail if XFRMA_IF_ID 0" Kai Lüke
2022-03-01 6:43 ` Jakub Kicinski
2022-03-01 13:12 ` Kai Lüke [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-01 13:15 [PATCH 1/2] Revert "xfrm: interface with if_id 0 should return error" kailueke
2022-03-01 13:15 ` [PATCH 2/2] Revert "xfrm: state and policy should fail if XFRMA_IF_ID 0" kailueke
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=0d449d5b-e169-cd9f-0731-9a45b25da3cb@linux.microsoft.com \
--to=kailueke@linux.microsoft.com \
--cc=eyal.birger@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@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 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.