Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Jianmin Wang <jianmin@iscas.ac.cn>
To:     gregkh@linuxfoundation.org
Cc:     davem@davemloft.net, dzickus@redhat.com,
        herbert@gondor.apana.org.au, jianmin@iscas.ac.cn,
        linux-crypto@vger.kernel.org, netdev@vger.kernel.org,
        omosnace@redhat.com, smueller@chronox.de, stable@vger.kernel.org,
        steffen.klassert@secunet.com
Subject: Re: Re: [PATCH] backports: crypto user - make NETLINK_CRYPTO work
Date:   Fri,  9 Apr 2021 13:14:57 +0000
Message-Id: <20210409131457.51384-1-jianmin@iscas.ac.cn>
In-Reply-To: <YG/11xcauoPY0sn+@kroah.com>
References: <YG/11xcauoPY0sn+@kroah.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Fri, Apr 09, 2021 at 08:36:07 +0200, Greg KH
> On Thu, Apr 08, 2021 at 07:11:48PM +0000, Jianmin Wang wrote:
> > while the new services need to invoke libkcapi in the container environment.
> > 
> > We have verified that the problem doesn't exist on newer kernel version. 
> > However, due to many services and the cluster running on many server machines 
> > whose host os are long-term linux distribution with linux 4.19 kernel, it will 
> > cost too much to migrate them to newer os with newer kernel version. This is 
> > why we need to fix the problem on linux 4.19.
>
> But this is not a regression, but rather a "resolve an issue that has
> never worked for new hardware", right?
> 
> And for that, moving to a new kernel seems like a wise thing to do to
> me because we do not like backporting new features.  Distro kernel are
> of course, free to do that if they wish.
> 
> thanks,
> 
> greg k-h

I understand. Thank you for your review and response.
--
Email: Jianmin Wang <jianmin@iscas.ac.cn>