public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Luis Chamberlain <mcgrof@kernel.org>,
	"linux-modules@vger.kernel.org" <linux-modules@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] Miscellaneous cleanups
Date: Tue, 22 Feb 2022 15:14:27 +0000	[thread overview]
Message-ID: <708fb1b3-e229-e9f6-48e7-500da8a894ef@csgroup.eu> (raw)
In-Reply-To: <cover.1645542447.git.christophe.leroy@csgroup.eu>



Le 22/02/2022 à 16:12, Christophe Leroy a écrit :
> This series applies on top of my series "Allocate module text and data separately" v5.
> 
> It does some cleanup around the settling of modules's layout page flags:
> - Make module_enable_x() independent of CONFIG_ARCH_HAS_STRICT_MODULE_RWX
> - Reunify everything into strict_rwx.c
> - Change big hammer BUG_ON()s into WARN_ON()s
> - Change misleading debug_align() to strict_align()

Seems like I made a big mess with v2.

I will resend it as v3.

Sorry for that.

Christophe

> 
> Changes in v2:
> - Rebased on top of my series "Allocate module text and data separately" v5
> - Moved the Kconfig patch out of this series, it is an independent change
> 
> Christophe Leroy (4):
>    module: Make module_enable_x() independent of
>      CONFIG_ARCH_HAS_STRICT_MODULE_RWX
>    module: Move module_enable_x() and frob_text() in strict_rwx.c
>    module: Rework layout alignment to avoid BUG_ON()s
>    module: Rename debug_align() as strict_align()
> 
>   kernel/module/Makefile     |  3 +-
>   kernel/module/internal.h   | 26 +++----------
>   kernel/module/kallsyms.c   |  4 +-
>   kernel/module/main.c       | 58 ++++++-----------------------
>   kernel/module/strict_rwx.c | 76 +++++++++++++++++++++++++++++++++-----
>   5 files changed, 88 insertions(+), 79 deletions(-)
> 

      parent reply	other threads:[~2022-02-22 15:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22 15:12 [PATCH v2 0/4] Miscellaneous cleanups Christophe Leroy
2022-02-22 15:12 ` [PATCH v2 1/4] module: Make module_enable_x() independent of CONFIG_ARCH_HAS_STRICT_MODULE_RWX Christophe Leroy
2022-02-22 15:12 ` [PATCH v2 2/4] module: Move module_enable_x() and frob_text() in strict_rwx.c Christophe Leroy
2022-02-22 15:12 ` [PATCH v2 3/4] module: Rework layout alignment to avoid BUG_ON()s Christophe Leroy
2022-02-22 15:12 ` [PATCH v2 4/4] module: Rename debug_align() as strict_align() Christophe Leroy
2022-02-22 15:14 ` Christophe Leroy [this message]

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=708fb1b3-e229-e9f6-48e7-500da8a894ef@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=mcgrof@kernel.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