From: Richard Weinberger <richard@nod.at>
To: Daniel Borkmann <dborkman@redhat.com>
Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] x86, um: actually mark system call tables readonly
Date: Sat, 03 Jan 2015 22:40:58 +0100 [thread overview]
Message-ID: <54A861EA.1070607@nod.at> (raw)
In-Reply-To: <1420287070-23450-1-git-send-email-dborkman@redhat.com>
Am 03.01.2015 um 13:11 schrieb Daniel Borkmann:
> Commit a074335a370e ("x86, um: Mark system call tables readonly") was
> supposed to mark the sys_call_table in UML as RO by adding the const,
> but it doesn't have the desired effect as it's nevertheless being placed
> into the data section since __cacheline_aligned enforces sys_call_table
> being placed into .data..cacheline_aligned instead. We need to use
> the ____cacheline_aligned version instead to fix this issue.
__ vs. ___ oh my...
I'll pick up this patch.
Thanks a lot Daniel!
//richard
next prev parent reply other threads:[~2015-01-03 21:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-03 12:11 [PATCH] x86, um: actually mark system call tables readonly Daniel Borkmann
2015-01-03 21:40 ` Richard Weinberger [this message]
2015-01-03 23:23 ` Daniel Borkmann
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=54A861EA.1070607@nod.at \
--to=richard@nod.at \
--cc=akpm@linux-foundation.org \
--cc=dborkman@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.