From: Greg KH <gregkh@linuxfoundation.org>
To: Oleksandr Tymoshenko <ovt@google.com>
Cc: srish.srinivasan@broadcom.com, ajay.kaher@broadcom.com,
alexey.makhalov@broadcom.com, borisp@nvidia.com,
davejwatson@fb.com, davem@davemloft.net, edumazet@google.com,
horms@kernel.org, john.fastabend@gmail.com, kuba@kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com, sashal@kernel.org,
sd@queasysnail.net, stable@vger.kernel.org, vakul.garg@nxp.com,
vasavi.sirnapalli@broadcom.com
Subject: Re: [PATCH 6.1.y] net: tls: handle backlogging of crypto requests
Date: Tue, 21 May 2024 17:26:02 +0200 [thread overview]
Message-ID: <2024052144-improper-quarterly-0852@gregkh> (raw)
In-Reply-To: <20240521105838.2239567-1-ovt@google.com>
On Tue, May 21, 2024 at 10:58:38AM +0000, Oleksandr Tymoshenko wrote:
> Hello,
>
> As far as I understand this issue also affects kernel 5.15. Are there any plans
> to backport it to 5.15?
Why not provide a working backport if you are interested in the 5.15.y
kernel tree?
thanks,
greg k-h
next prev parent reply other threads:[~2024-05-21 15:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 12:38 [PATCH 6.1.y] net: tls: handle backlogging of crypto requests Srish Srinivasan
2024-03-29 9:23 ` Greg KH
2024-03-29 10:25 ` [PATCH v2 " Srish Srinivasan
2024-03-29 11:49 ` Greg KH
2024-03-29 10:32 ` [PATCH " Srish Srinivasan
2024-03-29 11:48 ` Greg KH
2024-05-21 10:58 ` Oleksandr Tymoshenko
2024-05-21 15:26 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-08 16:48 [PATCH] NFSv4: fix a mount deadlock in NFS v4.1 client Trond Myklebust
2024-09-09 16:36 ` [PATCH 6.1.y] net: tls: handle backlogging of crypto requests Oleksandr Tymoshenko
2024-09-09 17:56 ` Trond Myklebust
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=2024052144-improper-quarterly-0852@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ajay.kaher@broadcom.com \
--cc=alexey.makhalov@broadcom.com \
--cc=borisp@nvidia.com \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ovt@google.com \
--cc=pabeni@redhat.com \
--cc=sashal@kernel.org \
--cc=sd@queasysnail.net \
--cc=srish.srinivasan@broadcom.com \
--cc=stable@vger.kernel.org \
--cc=vakul.garg@nxp.com \
--cc=vasavi.sirnapalli@broadcom.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.