Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: "Wentao Guan" <guanwentao@uniontech.com>
To: "Greg KH" <gregkh@linuxfoundation.org>
Cc: hexlabsecurity <hexlabsecurity@proton.me>,
	paul <paul@paul-moore.com>, "Sasha Levin" <sashal@kernel.org>,
	stable <stable@vger.kernel.org>,
	"stephen.smalley.work" <stephen.smalley.work@gmail.com>
Subject: Re: [PATCH 6.18.47-rc1 01/10] Revert "selinux: require a class's permission values to cover its permission count"
Date: Thu, 27 Aug 2026 18:37:06 +0800	[thread overview]
Message-ID: <tencent_13FEDEFE3555FA9325EE9C35@qq.com> (raw)
In-Reply-To: <2026082752-aviator-isolating-5239@gregkh>

> Again, I am totally confused.  I'll go drop ALL of the selinux changes
> in ALL of the queues and wait for the next round of releases before I
> pick up the above ones (and we need that same series for older trees
too.)

OK, I will take a look for older tree and send backports.

BRs
Wentao Guan

  reply	other threads:[~2026-08-27 10:37 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 10:41 FAILED: patch "[PATCH] selinux: require a class's permission values to cover its" failed to apply to 6.18-stable tree gregkh
2026-08-24 22:00 ` [PATCH 6.18.y 1/3] selinux: use u16 for security classes Sasha Levin
2026-08-24 22:00   ` [PATCH 6.18.y 2/3] selinux: more strict policy parsing Sasha Levin
2026-08-24 22:00   ` [PATCH 6.18.y 3/3] selinux: require a class's permission values to cover its permission count Sasha Levin
2026-08-25 10:02     ` Wentao Guan
2026-08-25 10:03     ` [PATCH 6.18.y 1/7] Revert "selinux: reject a permission value exceeding the class permission count" Wentao Guan
2026-08-27  5:17       ` Sasha Levin
2026-08-27  5:47         ` [PATCH 7.1.y 1/5] selinux: use u16 for security classes Wentao Guan
2026-08-27  5:47         ` [PATCH 7.1.y 2/5] selinux: more strict policy parsing Wentao Guan
2026-08-27  5:47         ` [PATCH 7.1.y 3/5] selinux: reject a permission value exceeding the class permission count Wentao Guan
2026-08-27  5:47         ` [PATCH 7.1.y 4/5] selinux: reject a class permission count below its inherited common Wentao Guan
2026-08-27  5:47         ` [PATCH 7.1.y 5/5] selinux: require a class's permission values to cover its permission count Wentao Guan
2026-08-27  8:37         ` [PATCH 6.18.47-rc1 01/10] Revert "selinux: require a class's permission values to cover its permission count" Wentao Guan
2026-08-27  8:59           ` Greg KH
2026-08-27  9:06             ` [PATCH 6.6 00/87] 6.6.154-rc1 review Wentao Guan
2026-08-27  9:07             ` [PATCH 6.18.47-rc1 01/10] Revert "selinux: require a class's permission values to cover its permission count" Wentao Guan
2026-08-27  9:23               ` Greg KH
2026-08-27  9:32                 ` Wentao Guan
2026-08-27 10:32                   ` Greg KH
2026-08-27 10:37                     ` Wentao Guan [this message]
2026-08-27  8:37         ` [PATCH 6.18.47-rc1 02/10] Revert "selinux: more strict policy parsing" Wentao Guan
2026-08-27  8:38         ` [PATCH 6.18.47-rc1 03/10] Revert "selinux: use u16 for security classes" Wentao Guan
2026-08-27  8:58           ` Greg KH
2026-08-27  9:17             ` Wentao Guan
2026-08-27  8:38         ` [PATCH 6.18.y 04/10] Revert "selinux: reject a permission value exceeding the class permission count" Wentao Guan
2026-08-27  8:38         ` [PATCH 6.18.y 05/10] Revert "selinux: reject a class permission count below its inherited common" Wentao Guan
2026-08-27  8:38         ` [PATCH 6.18.y 06/10] selinux: use u16 for security classes Wentao Guan
2026-08-27  8:38         ` [PATCH 6.18.y 07/10] selinux: more strict policy parsing Wentao Guan
2026-08-27  8:38         ` [PATCH 6.18.y 08/10] selinux: reject a permission value exceeding the class permission count Wentao Guan
2026-08-27  8:38         ` [PATCH 6.18.y 09/10] selinux: reject a class permission count below its inherited common Wentao Guan
2026-08-27  8:38         ` [PATCH 6.18.y 10/10] selinux: require a class's permission values to cover its permission count Wentao Guan
2026-08-25 10:03     ` [PATCH 6.18.y 2/7] Revert "selinux: reject a class permission count below its inherited common" Wentao Guan
2026-08-25 10:03     ` [PATCH 6.18.y 3/7] selinux: use u16 for security classes Wentao Guan
2026-08-25 10:03     ` [PATCH 6.18.y 4/7] selinux: more strict policy parsing Wentao Guan
2026-08-25 10:03     ` [PATCH 6.18.y 5/7] selinux: reject a permission value exceeding the class permission count Wentao Guan
2026-08-25 10:03     ` [PATCH 6.18.y 6/7] selinux: reject a class permission count below its inherited common Wentao Guan
2026-08-25 10:03     ` [PATCH 6.18.y 7/7] selinux: require a class's permission values to cover its permission count Wentao Guan

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=tencent_13FEDEFE3555FA9325EE9C35@qq.com \
    --to=guanwentao@uniontech.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hexlabsecurity@proton.me \
    --cc=paul@paul-moore.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=stephen.smalley.work@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox