From: Nathan_Lynch@mentor.com (Nathan Lynch)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 01/10] ARM: use _install_special_mapping for sigpage
Date: Mon, 4 Aug 2014 08:12:26 -0500 [thread overview]
Message-ID: <53DF86BA.2030207@mentor.com> (raw)
In-Reply-To: <20140804124630.GG15117@arm.com>
On 08/04/2014 07:46 AM, Will Deacon wrote:
> On Sat, Aug 02, 2014 at 07:16:38PM +0100, Nathan Lynch wrote:
>> _install_special_mapping allows the VMA to be identifed in
>> /proc/pid/maps without the use of arch_vma_name, providing a
>> slight net reduction in object size:
>>
>> text data bss dec hex filename
>> 2996 96 144 3236 ca4 arch/arm/kernel/process.o (before)
>> 2956 104 144 3204 c84 arch/arm/kernel/process.o (after)
>>
>> Signed-off-by: Nathan Lynch <nathan_lynch@mentor.com>
>> Reviewed-by: Kees Cook <keescook@chromium.org>
>> ---
>> arch/arm/kernel/process.c | 24 ++++++++++++++++--------
>> 1 file changed, 16 insertions(+), 8 deletions(-)
>>
>> diff --git a/arch/arm/kernel/process.c b/arch/arm/kernel/process.c
>> index 81ef686a91ca..46fbbb3701a0 100644
>> --- a/arch/arm/kernel/process.c
>> +++ b/arch/arm/kernel/process.c
>> @@ -472,19 +472,23 @@ int in_gate_area_no_mm(unsigned long addr)
>>
>> const char *arch_vma_name(struct vm_area_struct *vma)
>> {
>> - return is_gate_vma(vma) ? "[vectors]" :
>> - (vma->vm_mm && vma->vm_start == vma->vm_mm->context.sigpage) ?
>> - "[sigpage]" : NULL;
>> + return is_gate_vma(vma) ? "[vectors]" : NULL;
>> }
>
> Why do you need this function? I just removed it for arm64 and I think x86
> has done the same.
I think arch_vma_name is still needed for arm as long as the vectors
page is not installed using _install_special_mapping. I'm honestly not
sure whether moving the vectors page to that API would be appropriate,
but it would be a larger undertaking.
next prev parent reply other threads:[~2014-08-04 13:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-02 18:16 [PATCH v8 00/10] ARM: VDSO Nathan Lynch
2014-08-02 18:16 ` [PATCH v8 01/10] ARM: use _install_special_mapping for sigpage Nathan Lynch
2014-08-04 12:46 ` Will Deacon
2014-08-04 13:12 ` Nathan Lynch [this message]
2014-08-04 14:11 ` Nathan Lynch
2014-08-04 16:06 ` Will Deacon
2014-08-02 18:16 ` [PATCH v8 02/10] ARM: place sigpage at a random offset above stack Nathan Lynch
2014-08-02 18:16 ` [PATCH v8 03/10] clocksource: arm_arch_timer: change clocksource name if CP15 unavailable Nathan Lynch
2014-08-05 0:01 ` Stephen Boyd
2014-08-05 0:10 ` Andy Lutomirski
2014-08-02 18:16 ` [PATCH v8 04/10] clocksource: arm_arch_timer: enable counter access for 32-bit ARM Nathan Lynch
2014-08-02 18:16 ` [PATCH v8 05/10] ARM: arch_timer: remove unused functions Nathan Lynch
2014-08-04 12:49 ` Will Deacon
2014-08-04 13:29 ` Nathan Lynch
2014-08-04 16:05 ` Will Deacon
2014-08-02 18:16 ` [PATCH v8 06/10] arm64: " Nathan Lynch
2014-08-02 18:16 ` [PATCH v8 07/10] ARM: miscellaneous vdso infrastructure, preparation Nathan Lynch
2014-08-02 18:16 ` [PATCH v8 08/10] ARM: add vdso user-space code Nathan Lynch
2014-08-02 18:16 ` [PATCH v8 09/10] ARM: vdso initialization, mapping, and synchronization Nathan Lynch
2014-08-02 18:16 ` [PATCH v8 10/10] ARM: add CONFIG_VDSO Kconfig and Makefile bits Nathan Lynch
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=53DF86BA.2030207@mentor.com \
--to=nathan_lynch@mentor.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).