From: Paul Moore <paul@paul-moore.com>
To: Kees Cook <kees@kernel.org>
Cc: linux-security-module@vger.kernel.org, linux-mm@kvack.org,
lorenzo.stoakes@oracle.com
Subject: Re: [PATCH] lsm: preserve /proc/sys/vm/mmap_min_addr when !CONFIG_SECURITY
Date: Fri, 30 Jan 2026 11:48:19 -0500 [thread overview]
Message-ID: <CAHC9VhS77c1-5HTRUVXV=e2Z7Q3wHeo_e8S3RswqGWLTB0_ZhQ@mail.gmail.com> (raw)
In-Reply-To: <202601291730.45120C1A@keescook>
On Thu, Jan 29, 2026 at 8:31 PM Kees Cook <kees@kernel.org> wrote:
> On Thu, Jan 29, 2026 at 05:51:33PM -0500, Paul Moore wrote:
> > While reworking the LSM initialization code the
> > /proc/sys/vm/mmap_min_addr handler was inadvertently caught up in the
> > change and the procfs entry wasn't setup when CONFIG_SECURITY was not
> > selected at kernel build time. This patch restores the previous behavior
> > and ensures that the procfs entry is setup regardless of the
> > CONFIG_SECURITY state.
> >
> > Future work will improve upon this, likely by moving the procfs handler
> > into the mm subsystem, but this patch should resolve the immediate
> > regression.
> >
> > Fixes: 4ab5efcc2829 ("lsm: consolidate all of the LSM framework initcalls")
> > Reported-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> > Signed-off-by: Paul Moore <paul@paul-moore.com>
>
> Good catch and fix!
>
> Reviewed-by: Kees Cook <kees@kernel.org>
Merged into lsm/stable-6.19, with plans to send this to Linus early
next week after a day or two in linux-next. Thanks everyone!
--
paul-moore.com
next prev parent reply other threads:[~2026-01-30 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 22:51 Paul Moore
2026-01-30 1:31 ` Kees Cook
2026-01-30 16:48 ` Paul Moore [this message]
2026-02-02 10:53 ` Lorenzo Stoakes
2026-02-02 16:19 ` Paul Moore
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='CAHC9VhS77c1-5HTRUVXV=e2Z7Q3wHeo_e8S3RswqGWLTB0_ZhQ@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=kees@kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.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