From: Christoph Hellwig <hch@infradead.org>
To: Will Deacon <will@kernel.org>
Cc: sanggil2.kim@samsung.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: kernel: Add module symbols _text, _etext.
Date: Thu, 9 Jul 2020 12:01:07 +0100 [thread overview]
Message-ID: <20200709110107.GA12046@infradead.org> (raw)
In-Reply-To: <20200709094950.GA28361@willie-the-truck>
On Thu, Jul 09, 2020 at 10:49:51AM +0100, Will Deacon wrote:
> On Thu, Jul 09, 2020 at 05:23:45PM +0900, sanggil2.kim@samsung.com wrote:
> > From: Sanggil Kim <sanggil2.kim@samsung.com>
> >
> > We have a solution to protect kernel code section(autually from _text to
> > _etext) by not MMU. In order to do this, we have to know the addresses
> > of _text and _etext at runtime.
>
> Interesting! Can you post patches so that we can implement this solution
> upstream? Without an in-tree user, we won't be exporting these symbols.
And even with that I'm pretty sure the code doing the 'protection'
should be built-in and not modular..
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-07-09 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200709082408epcas2p4369fa8f06a57c7358be38282aae0f501@epcas2p4.samsung.com>
2020-07-09 8:23 ` [PATCH] arm64: kernel: Add module symbols _text, _etext sanggil2.kim
2020-07-09 9:49 ` Will Deacon
2020-07-09 11:01 ` Christoph Hellwig [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=20200709110107.GA12046@infradead.org \
--to=hch@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sanggil2.kim@samsung.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).