From: David Laight <David.Laight@ACULAB.COM>
To: "'Segher Boessenkool'" <segher@kernel.crashing.org>,
Kees Cook <keescook@chromium.org>
Cc: Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Jinbum Park <jinb.park7@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: RE: [PATCH] mm: fix RODATA_TEST failure "rodata_test: test data was not read only"
Date: Mon, 25 Sep 2017 16:01:55 +0000 [thread overview]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6DD007F58B@AcuExch.aculab.com> (raw)
In-Reply-To: <20170925073721.GM8421@gate.crashing.org>
From: Segher Boessenkool
> Sent: 25 September 2017 08:37
> On Sun, Sep 24, 2017 at 12:17:51PM -0700, Kees Cook wrote:
> > On Thu, Sep 21, 2017 at 2:37 AM, Christophe Leroy
> > <christophe.leroy@c-s.fr> wrote:
> > > On powerpc, RODATA_TEST fails with message the following messages:
> > >
> > > [ 6.199505] Freeing unused kernel memory: 528K
> > > [ 6.203935] rodata_test: test data was not read only
> > >
> > > This is because GCC allocates it to .data section:
> > >
> > > c0695034 g O .data 00000004 rodata_test_data
> >
> > Uuuh... that seems like a compiler bug. It's marked "const" -- it
> > should never end up in .data. I would argue that this has done exactly
> > what it was supposed to do, and shows that something has gone wrong.
> > It should always be const. Adding "static" should just change
> > visibility. (I'm not opposed to the static change, but it seems to
> > paper over a problem with the compiler...)
>
> The compiler puts this item in .sdata, for 32-bit. There is no .srodata,
> so if it wants to use a small data section, it must use .sdata .
>
> Non-external, non-referenced symbols are not put in .sdata, that is the
> difference you see with the "static".
>
> I don't think there is a bug here. If you think there is, please open
> a GCC bug.
The .sxxx sections are for 'small' data that can be accessed (typically)
using small offsets from a global register.
This means that all sections must be adjacent in the image.
So you can't really have readonly small data.
My guess is that the linker script is putting .srodata in with .sdata.
David
next prev parent reply other threads:[~2017-09-25 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 9:37 [PATCH] mm: fix RODATA_TEST failure "rodata_test: test data was not read only" Christophe Leroy
2017-09-24 19:17 ` Kees Cook
2017-09-25 7:37 ` Segher Boessenkool
2017-09-25 16:01 ` David Laight [this message]
2017-09-25 19:41 ` Segher Boessenkool
2017-10-02 19:29 ` Kees Cook
2017-10-02 20:08 ` Segher Boessenkool
2017-10-02 20:27 ` Kees Cook
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=063D6719AE5E284EB5DD2968C1650D6DD007F58B@AcuExch.aculab.com \
--to=david.laight@aculab.com \
--cc=akpm@linux-foundation.org \
--cc=jinb.park7@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=segher@kernel.crashing.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).