public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jessica Yu <jeyu@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] Modules updates for v5.13
Date: Wed, 28 Apr 2021 14:58:44 +0200	[thread overview]
Message-ID: <YIlcBHhuR9LvKZ7q@gunter> (raw)

Hi Linus,

Please pull below to receive modules updates for the v5.13 merge window.
A summary can be found in the signed tag.

Thank you,

Jessica

--
The following changes since commit 1e28eed17697bcf343c6743f0028cc3b5dd88bf0:

   Linux 5.12-rc3 (2021-03-14 14:41:02 -0700)

are available in the Git repository at:

   git://git.kernel.org/pub/scm/linux/kernel/git/jeyu/linux.git tags/modules-for-v5.13

for you to fetch changes up to 33121347fb1c359bd6e3e680b9f2c6ced5734a81:

   module: treat exit sections the same as init sections when !CONFIG_MODULE_UNLOAD (2021-03-29 13:08:53 +0200)

----------------------------------------------------------------
Modules updates for v5.13

Summary of modules changes for the 5.13 merge window:

- Fix an age old bug involving jump_calls and static_labels when
   CONFIG_MODULE_UNLOAD=n. When CONFIG_MODULE_UNLOAD=n, it means you
   can't unload modules, so normally the __exit sections of a module are
   not loaded at all. However, dynamic code patching (jump_label,
   static_call, alternatives) can have sites in __exit sections even if
   __exit is never executed.

   Reported by Peter Zijlstra: "Alternatives, jump_labels and static_call
   all can have relocations into __exit code.  Not loading it at all would
   be BAD." Therefore, load the __exit sections even when
   CONFIG_MODULE_UNLOAD=n, and discard them after init.

Signed-off-by: Jessica Yu <jeyu@kernel.org>

----------------------------------------------------------------
Jessica Yu (1):
       module: treat exit sections the same as init sections when !CONFIG_MODULE_UNLOAD

  kernel/module.c | 9 ++++-----
  1 file changed, 4 insertions(+), 5 deletions(-)

             reply	other threads:[~2021-04-28 12:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28 12:58 Jessica Yu [this message]
2021-04-29 11:37 ` [GIT PULL] Modules updates for v5.13 Jessica Yu
2021-04-30 19:37 ` Linus Torvalds
2021-05-03 10:13   ` Jessica Yu
2021-04-30 19:38 ` 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=YIlcBHhuR9LvKZ7q@gunter \
    --to=jeyu@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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