[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <01cb28cb-56b7-4862-bf27-07e4bf17115e@lucifer.local>
Date: Thu, 29 Jan 2026 17:09:51 +0000
From: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
To: Vlastimil Babka <vbabka@...e.cz>
Cc: Paul Moore <paul@...l-moore.com>, linux-security-module@...r.kernel.org,
linux-integrity@...r.kernel.org, selinux@...r.kernel.org,
john.johansen@...onical.com, zohar@...ux.ibm.com,
roberto.sassu@...wei.com, wufan@...nel.org, mic@...ikod.net,
gnoack@...gle.com, kees@...nel.org, mortonm@...omium.org,
casey@...aufler-ca.com, penguin-kernel@...ove.sakura.ne.jp,
nicolas.bouchinet@....cyber.gouv.fr, xiujianfeng@...wei.com,
linux-mm <linux-mm@...ck.org>, David Hildenbrand <david@...hat.com>,
"Liam R. Howlett" <Liam.Howlett@...cle.com>,
Mike Rapoport <rppt@...nel.org>,
Suren Baghdasaryan <surenb@...gle.com>, Michal Hocko <mhocko@...e.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 10/11] lsm: consolidate all of the LSM framework
initcalls
On Thu, Jan 29, 2026 at 06:02:00PM +0100, Vlastimil Babka wrote:
> Agreed, the mmap_min_addr should stay visible and applied unconditionally.
> AFAICS the only relation to SECURITY/LSM is whether CONFIG_LSM_MMAP_MIN_ADDR
> is used as an additional lower limit to both CONFIG_DEFAULT_MMAP_MIN_ADDR
> and the sysctl-written value?
Thanks, yeah we should probably actually move the non-LSM-relevant stuff
out to mm to be honest.
But that's future work, for an -rc8 hotfix we need to make the init of this
particular module not dependent on normal LSM initialisation, as horrid as
that is...
Cheers, Lorenzo
Powered by blists - more mailing lists