From: Greg KH <gregkh@linuxfoundation.org>
To: Dragos-Marian Panait <dragos.panait@windriver.com>
Cc: stable@vger.kernel.org, wenxu <wenxu@ucloud.cn>,
Jakub Kicinski <kuba@kernel.org>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Davide Caratti <dcaratti@redhat.com>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Paolo Abeni <pabeni@redhat.com>, William Zhao <wizhao@redhat.com>,
Xin Long <lucien.xin@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>, Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 5.10 0/3] Fix for CVE-2022-4269
Date: Fri, 26 May 2023 19:27:26 +0100 [thread overview]
Message-ID: <2023052617-preorder-universal-1b5d@gregkh> (raw)
In-Reply-To: <20230516190040.636627-1-dragos.panait@windriver.com>
On Tue, May 16, 2023 at 10:00:37PM +0300, Dragos-Marian Panait wrote:
> The following commits are needed to fix CVE-2022-4269:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fa6d639930ee5cd3f932cc314f3407f07a06582d
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=78dcdffe0418ac8f3f057f26fe71ccf4d8ed851f
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ca22da2fbd693b54dc8e3b7b54ccc9f7e9ba3640
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-05-26 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 19:00 [PATCH 5.10 0/3] Fix for CVE-2022-4269 Dragos-Marian Panait
2023-05-16 19:00 ` [PATCH 5.10 1/3] net/sched: act_mirred: refactor the handle of xmit Dragos-Marian Panait
2023-05-16 19:00 ` [PATCH 5.10 2/3] net/sched: act_mirred: better wording on protection against excessive stack growth Dragos-Marian Panait
2023-05-16 19:00 ` [PATCH 5.10 3/3] act_mirred: use the backlog for nested calls to mirred ingress Dragos-Marian Panait
2023-05-26 18:27 ` 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=2023052617-preorder-universal-1b5d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=dragos.panait@windriver.com \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wenxu@ucloud.cn \
--cc=wizhao@redhat.com \
--cc=xiyou.wangcong@gmail.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.