From: Christoph Hellwig <hch@lst.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Nicholas Piggin <npiggin@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: small ioremap cleanups
Date: Tue, 24 Aug 2021 11:12:57 +0200 [thread overview]
Message-ID: <20210824091259.1324527-1-hch@lst.de> (raw)
Hi Andrew,
the first patch moves a little code around the vmalloc/ioremap
boundary followed a bigger move by Nick earlier. The second
enforces non-executable mapping on ioremap just like we do
for vmap. No driver currently uses executable mappings anyway,
as they should.
next reply other threads:[~2021-08-24 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 9:12 Christoph Hellwig [this message]
2021-08-24 9:12 ` [PATCH 1/2] mm: move ioremap_page_range to vmalloc.c Christoph Hellwig
2021-08-24 19:51 ` kernel test robot
2021-08-26 2:36 ` Nicholas Piggin
2021-08-24 9:12 ` [PATCH 2/2] mm: don't allow executable ioremap mappings Christoph Hellwig
2021-08-26 2:46 ` Nicholas Piggin
2021-08-26 5:37 ` Christoph Hellwig
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=20210824091259.1324527-1-hch@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@gmail.com \
--cc=peterz@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).