linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] arm64: Cleanups if modules are disabled
Date: Wed, 13 Sep 2017 00:13:46 +0100	[thread overview]
Message-ID: <20170912231345.GF10675@arm.com> (raw)
In-Reply-To: <1504634813-29554-1-git-send-email-geert+renesas@glider.be>

On Tue, Sep 05, 2017 at 08:06:51PM +0200, Geert Uytterhoeven wrote:
> 	Hi Catalin, Will,
> 
> This patch series disables printing and reservation of virtual memory for
> modules if module support is disabled.

If we're going to do this, then we should probably also update the pt
dumping code (mm/dump.c) to avoid dumping the modules area too.

There are also some weird consequences of defining MODULES_VSIZE to be 0,
since we'll end up registering a zero-length region with KASAN and
calculating a bogus module_alloc_base in the kaslr code. This might all be
harmless, but it feels like we're laying down some tripwires for ourselves
that I'd rather avoid doing.

Will

      reply	other threads:[~2017-09-12 23:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05 18:06 [PATCH 0/2] arm64: Cleanups if modules are disabled Geert Uytterhoeven
2017-09-12 23:13 ` Will Deacon [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=20170912231345.GF10675@arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).