mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Petr Pavlu <petr.pavlu@suse.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
	Sami Tolvanen <samitolvanen@google.com>,
	Daniel Gomez <da.gomez@samsung.com>,
	linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
	Valentin Schneider <vschneid@redhat.com>
Subject: [GIT PULL] Modules changes for v6.16-rc1
Date: Mon, 2 Jun 2025 16:34:45 +0200	[thread overview]
Message-ID: <458901be-1da8-4987-9c72-5aa3da6db15e@suse.com> (raw)

The following changes since commit 82f2b0b97b36ee3fcddf0f0780a9a0825d52fec3:

  Linux 6.15-rc6 (2025-05-11 14:54:11 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/modules/linux.git/ tags/modules-6.16-rc1

for you to fetch changes up to a0b018a495a3f68693e45ab570fae8191d907d86:

  module: Remove outdated comment about text_size (2025-05-18 13:56:22 +0200)

----------------------------------------------------------------
Modules changes for 6.16-rc1

- Make .static_call_sites in modules read-only after init

  The .static_call_sites sections in modules have been made read-only after
  init to avoid any (non-)accidental modifications, similarly to how they
  are read-only after init in vmlinux.

- The rest are minor cleanups.

The changes have been on linux-next for 2 months, with the exception of the
last comment-only cleanup.

As discussed previously, we rotate module maintainership among its
co-maintainers every 6 months. Daniel Gomez is next in line and he will
send the next pull request for the modules.

----------------------------------------------------------------
Petr Pavlu (3):
      module: Constify parameters of module_enforce_rwx_sections()
      module: Add a separate function to mark sections as read-only after init
      module: Make .static_call_sites read-only after init

Valentin Schneider (1):
      module: Remove outdated comment about text_size

 kernel/module/internal.h   |  7 +++++--
 kernel/module/main.c       | 27 +++++++-------------------
 kernel/module/strict_rwx.c | 47 ++++++++++++++++++++++++++++++++++++++++++++--
 3 files changed, 57 insertions(+), 24 deletions(-)

             reply	other threads:[~2025-06-02 14:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-02 14:34 Petr Pavlu [this message]
2025-06-03  0:45 ` pr-tracker-bot

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=458901be-1da8-4987-9c72-5aa3da6db15e@suse.com \
    --to=petr.pavlu@suse.com \
    --cc=da.gomez@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=samitolvanen@google.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vschneid@redhat.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

all inboxes | Powered by JetHome®