Re: [tip:x86/vdso] x86-64: Allow alternative patching in the vDSO
From: Andrew Lutomirski
Date: Mon Jul 18 2011 - 15:54:52 EST
On Mon, Jul 18, 2011 at 3:10 PM, Borislav Petkov <bp@xxxxxxxxx> wrote:
> On Fri, Jul 15, 2011 at 04:23:18AM +0000, tip-bot for Andy Lutomirski wrote:
>> Commit-ID: 1b3f2a72bbcfdf92e368a44448c45eb639b05b5e
>> Gitweb: http://git.kernel.org/tip/1b3f2a72bbcfdf92e368a44448c45eb639b05b5e
>> Author: Andy Lutomirski <luto@xxxxxxx>
>> AuthorDate: Wed, 13 Jul 2011 09:24:11 -0400
>> Committer: H. Peter Anvin <hpa@xxxxxxxxxxxxxxx>
>> CommitDate: Wed, 13 Jul 2011 11:23:07 -0700
>> x86-64: Allow alternative patching in the vDSO
>> This code is short enough and different enough from the module
>> loader that it's not worth trying to share anything.
>> Signed-off-by: Andy Lutomirski <luto@xxxxxxx>
>> Link: http://lkml.kernel.org/r/e73112e4381fff29e31b882c2d0856822edaea53.1310563276.git.luto@xxxxxxx
>> Signed-off-by: H. Peter Anvin <hpa@xxxxxxxxxxxxxxx>
> From: Borislav Petkov <bp@xxxxxxxxx>
> Date: Mon, 18 Jul 2011 21:07:25 +0200
> Subject: [PATCH] x86, vdso: Drop now wrong comment
> Now that 1b3f2a72bbcfdf92e368a44448c45eb639b05b5e is in, it is very
> important that the below lying comment be removed! :-)
> Signed-off-by: Borislav Petkov <bp@xxxxxxxxx>
> arch/x86/vdso/vclock_gettime.c | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
> diff --git a/arch/x86/vdso/vclock_gettime.c b/arch/x86/vdso/vclock_gettime.c
> index 8792d6e..6bc0e72 100644
> --- a/arch/x86/vdso/vclock_gettime.c
> +++ b/arch/x86/vdso/vclock_gettime.c
> @@ -6,7 +6,6 @@
> * The code should have no internal unresolved relocations.
> * Check with readelf after changing.
> - * Also alternative() doesn't work.
That was the whole point, after all.
Acked-by: Andy Lutomirski <luto@xxxxxxx>
> /* Disable profiling for userspace code: */
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/