From: Greg KH <gregkh@linuxfoundation.org>
To: Kai Lueke <kailueke@linux.microsoft.com>
Cc: stable@vger.kernel.org
Subject: Re: xfrm regression in 5.10.94
Date: Tue, 1 Mar 2022 20:38:21 +0100 [thread overview]
Message-ID: <Yh52LSGjBz+yF/HO@kroah.com> (raw)
In-Reply-To: <e8d57c20-56f8-f457-1db5-e6d5ed9618b6@linux.microsoft.com>
On Tue, Mar 01, 2022 at 05:34:00PM +0100, Kai Lueke wrote:
> Hi,
> > Why is 5.10 special and newer kernels are not? This change shows up for
> > them, right? Either this is a regression for all kernel releases and
> > needs to be resolved, or it is ok for any kernel release.
> >
> > Please work with the networking developers to either resolve the
> > regression of determine what needs to be done here for userspace to work
> > properly.
>
> I agree, thanks. I tried it
> (https://marc.info/?t=164607426900002&r=1&w=2) and got this response
> from Steffen Klassert now:
>
> > In general I agree that the userspace ABI has to be stable, but
> > this never worked. We changed the behaviour from silently broken to
> > notify userspace about a misconfiguration.
> >
> > It is the question what is more annoying for the users. A bug that
> > we can never fix, or changing a broken behaviour to something that
> > tells you at least why it is not working.
> >
> > In such a case we should gauge what's the better solution. Here
> > I tend to keep it as it is.
> (https://marc.info/?l=linux-netdev&m=164615098503579&w=2)
>
> Given it's unlikely to have this reverted in general I personally think
> that reverting for the LTS kernels makes sense at least...
Again, there is nothing "special" about LTS kernels for stuff like this.
It's fixing a bug that the kernel developers wanted to have fixed, and
so it gets backported everywhere relevant.
If I were to somehow "wait" on taking this, it's only delaying your
fixes from ever happening :)
thanks,
greg k-h
prev parent reply other threads:[~2022-03-01 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 12:22 xfrm regression in 5.10.94 Kai Lüke
2022-02-28 17:16 ` Greg KH
2022-03-01 16:34 ` Kai Lueke
2022-03-01 19:38 ` Greg KH [this message]
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=Yh52LSGjBz+yF/HO@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kailueke@linux.microsoft.com \
--cc=stable@vger.kernel.org \
/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