From: Alexander Graf <agraf@suse.de>
To: Zheng Xu <Zheng.Xu@arm.com>
Cc: Steve Capper <Steve.Capper@arm.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Mark Rutland <Mark.Rutland@arm.com>,
"mbrugger@suse.com" <mbrugger@suse.com>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <Will.Deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Stuart Monteith <Stuart.Monteith@arm.com>
Subject: Re: [PATCH] arm64: Add config to limit user space to 47bits
Date: Thu, 14 Jul 2016 10:01:50 +0200 [thread overview]
Message-ID: <45E0D3FF-FEC1-4A70-8B2D-A941A35788EB@suse.de> (raw)
In-Reply-To: <VI1PR0801MB142315FBEDD571CC23E8D7F796320@VI1PR0801MB1423.eurprd08.prod.outlook.com>
> Am 14.07.2016 um 09:49 schrieb Zheng Xu <Zheng.Xu@arm.com>:
>
> Sorry, I might misunderstand the issue. I thought there are still issues with master.
>
> I saw that you've mentioned there are pointers to .rodata. And I only fixed the heap. So I am just worried if there can be issues with .rodata. If pointers to .rodata are not tagged and used as js objects, it should be fine.
Please don't top post on kernel mailing lists.
The old Spidermonkey (which is used by couchdb) has some string allocation optimization in jsstr.cpp that directly pregenerates js strings in .rodata at compile time. Just try to run couchdb on a 48bit va aarch64 system and it will fall apart.
Fixing mozjs master doesn't really help here, since couchdb requires the ancient spidermonkey 1.8.5. An alternative to fixing that old js implementation would obviously also be to move couchdb to mozjs master.
Alex
next prev parent reply other threads:[~2016-07-14 8:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 15:42 [PATCH] arm64: Add config to limit user space to 47bits Alexander Graf
2016-07-13 15:59 ` Ard Biesheuvel
2016-07-13 16:14 ` Alexander Graf
2016-07-14 1:08 ` Steve Capper
2016-07-14 6:38 ` Alexander Graf
2016-07-14 7:03 ` Zheng Xu
2016-07-14 7:14 ` Alexander Graf
2016-07-14 7:49 ` Zheng Xu
2016-07-14 8:01 ` Alexander Graf [this message]
2016-07-14 18:07 ` Jeremy Linton
2016-07-14 15:17 ` Ard Biesheuvel
2016-07-13 16:10 ` Mark Rutland
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=45E0D3FF-FEC1-4A70-8B2D-A941A35788EB@suse.de \
--to=agraf@suse.de \
--cc=Catalin.Marinas@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=Steve.Capper@arm.com \
--cc=Stuart.Monteith@arm.com \
--cc=Will.Deacon@arm.com \
--cc=Zheng.Xu@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbrugger@suse.com \
/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).