Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Wentao Guan <guanwentao@uniontech.com>
Cc: hexlabsecurity@proton.me, paul@paul-moore.com, sashal@kernel.org,
	stable@vger.kernel.org, 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 12:32:14 +0200	[thread overview]
Message-ID: <2026082752-aviator-isolating-5239@gregkh> (raw)
In-Reply-To: <20260827093227.4050399-1-guanwentao@uniontech.com>

On Thu, Aug 27, 2026 at 05:32:27PM +0800, Wentao Guan wrote:
> > On Thu, Aug 27, 2026 at 05:07:59PM +0800, Wentao Guan wrote:
> > > Sorry for prev email title is garbaged...
> > > 
> > > > Why?  And this is not a real git id in the linux-stable tree.
> > > in stable-rc git tree.
> > > 
> > > > 
> > > > Do you want me to just drop all of the selinux patches from the 6.18.y
> > > > queue right now before I do the release?  I'll be glad to do so, but I
> > > > need to know why.
> > > 
> > > fair,
> > > 
> > > What happened in my side is Github Copliot review point out the issue:
> > > "This validation runs after symtab_insert(), so the table already owns key
> > > and perdatum. On an out-of-range value, the bad path frees both while leaving
> > > dangling pointers in the hash table, and rc is still 0, so malformed policy
> > > data is accepted and later accesses can use freed memory.
> > > Validate the value before inserting it and return -EINVAL."
> > 
> > I have no idea what that means at all as I can't parse LLM output well.
> > 
> > > In continues review, there LLM point out the mainline don`t had the issuse,
> > > for correct sequence is that git log --oneline
> > > (v6.18.46-1) selinux: require a class's permission values to cover its permission count
> > > selinux: reject a class permission count below its inherited common
> > > selinux: reject a permission value exceeding the class permission count
> > > selinux: more strict policy parsing
> > > selinux: use u16 for security classes
> > > Revert "selinux: reject a class permission count below its inherited common"
> > > Revert "selinux: reject a permission value exceeding the class permission count"
> > > (tag: v6.18.46, stable-gh/linux-6.18.y) Linux 6.18.46
> > > 
> > > This instead of Sasha`s series:
> > > 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
> > 
> > Ok, I'll drop these for now, and wait for your backports.
> > 
> > But note, I'll drop this for 6.18 and older, so I need backports for ALL
> > of those branches.
> 
> for 6.18.y:
> 1. https://lore.kernel.org/stable/20260825100338.4039846-1-guanwentao@uniontech.com/
> 2 .https://lore.kernel.org/stable/20260825100338.4039846-2-guanwentao@uniontech.com/
> 3 .https://lore.kernel.org/stable/20260825100338.4039846-3-guanwentao@uniontech.com/
> 4 .https://lore.kernel.org/stable/20260825100338.4039846-4-guanwentao@uniontech.com/
> 5 .https://lore.kernel.org/stable/20260825100338.4039846-5-guanwentao@uniontech.com/
> 6 .https://lore.kernel.org/stable/20260825100338.4039846-6-guanwentao@uniontech.com/
> 7 .https://lore.kernel.org/stable/20260825100338.4039846-7-guanwentao@uniontech.com/
> 
> for 7.1.y:
> 1. https://lore.kernel.org/stable/20260827054709.4027356-1-guanwentao@uniontech.com/
> 2. https://lore.kernel.org/stable/20260827054709.4027356-1-guanwentao@uniontech.com/
> 3. https://lore.kernel.org/stable/20260827054709.4027356-1-guanwentao@uniontech.com/
> 4. https://lore.kernel.org/stable/20260827054709.4027356-1-guanwentao@uniontech.com/
> 5. https://lore.kernel.org/stable/20260827054709.4027356-1-guanwentao@uniontech.com/
> 
> There only different between 6.18.y and 7.1.y are 6.18 revert which applied not
> cleanly:
> 62be2361da29505d3183da854f1c98d2e208e852
> 9f721b5d9e1d956ffe965bc09375989eb51881fd
> and next reapplied in next series cleanly.

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.)

thanks,

greg k-h

  reply	other threads:[~2026-08-27 10:32 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 [this message]
2026-08-27 10:37                     ` Wentao Guan
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=2026082752-aviator-isolating-5239@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=guanwentao@uniontech.com \
    --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