From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dong Chenchen <dongchenchen2@huawei.com>
Cc: kernel@openeuler.org, duanzi@zju.edu.cn, yuehaibing@huawei.com,
weiyongjun1@huawei.com, liujian56@huawei.com,
Laszlo Ersek <lersek@redhat.com>,
Eric Dumazet <edumazet@google.com>,
Lorenzo Colitti <lorenzo@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Pietro Borrello <borrello@diag.uniroma1.it>,
netdev@vger.kernel.org, stable@vger.kernel.org,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH OLK-5.10 v2 1/2] net: tun_chr_open(): set sk_uid from current_fsuid()
Date: Tue, 15 Aug 2023 17:14:27 +0200 [thread overview]
Message-ID: <2023081559-excursion-passion-07a3@gregkh> (raw)
In-Reply-To: <20230815135602.1014881-2-dongchenchen2@huawei.com>
On Tue, Aug 15, 2023 at 09:56:01PM +0800, Dong Chenchen wrote:
> From: Laszlo Ersek <lersek@redhat.com>
>
> stable inclusion
> from stable-v5.10.189
> commit 5ea23f1cb67e4468db7ff651627892c9217fec24
> category: bugfix
> bugzilla: 189104, https://gitee.com/src-openeuler/kernel/issues/I7QXHX
> CVE: CVE-2023-4194
>
> Reference: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5ea23f1cb67e4468db7ff651627892c9217fec24
Why are you not just merging directly from the LTS branches into your
tree? If you attempt to "cherry-pick" patches like this, you WILL miss
valid bugfixes.
thanks,
greg k-h
next prev parent reply other threads:[~2023-08-15 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230815135602.1014881-1-dongchenchen2@huawei.com>
2023-08-15 13:56 ` [PATCH OLK-5.10 v2 1/2] net: tun_chr_open(): set sk_uid from current_fsuid() Dong Chenchen
2023-08-15 15:14 ` Greg Kroah-Hartman [this message]
2023-08-15 13:56 ` [PATCH OLK-5.10 v2 2/2] net: tap_open(): " Dong Chenchen
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=2023081559-excursion-passion-07a3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=borrello@diag.uniroma1.it \
--cc=davem@davemloft.net \
--cc=dongchenchen2@huawei.com \
--cc=duanzi@zju.edu.cn \
--cc=edumazet@google.com \
--cc=kernel@openeuler.org \
--cc=lersek@redhat.com \
--cc=liujian56@huawei.com \
--cc=lorenzo@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=weiyongjun1@huawei.com \
--cc=yuehaibing@huawei.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.