linux-kernel - Re: [PATCH] x86_32,signal: Fix vdso rt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CALCETrU=FAXaebS3tJF7e_fx4DZzPK_FM_A9_OaoK-+WZDqPpA@mail.gmail.com>
Date:	Sat, 21 Jun 2014 08:43:44 -0700
From:	Andy Lutomirski <luto@...capital.net>
To:	Josh Boyer <jwboyer@...oraproject.org>,
	"H. Peter Anvin" <hpa@...or.com>
Cc:	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>,
	Andy Lutomirski <luto@...capital.net>
Subject: Re: [PATCH] x86_32,signal: Fix vdso rt_sigreturn

On Sat, Jun 21, 2014 at 7:31 AM, Andy Lutomirski <luto@...capital.net> wrote:
> This commit:
>
>     commit 6f121e548f83674ab4920a4e60afb58d4f61b829
>     Author: Andy Lutomirski <luto@...capital.net>
>     Date:   Mon May 5 12:19:34 2014 -0700
>
>         x86, vdso: Reimplement vdso.so preparation in build-time C
>
> Contained this obvious typo:
>
> -               restorer = VDSO32_SYMBOL(current->mm->context.vdso, rt_sigreturn);
> +               restorer = current->mm->context.vdso +
> +                       selected_vdso32->sym___kernel_sigreturn;
>
> Note the missing 'rt_' in the new code.  Fix it.
>
> Signed-off-by: Andy Lutomirski <luto@...capital.net>
> ---
>
> Compile-tested only.  I bet that someone will test it here far more quickly
> than I can figure out how to test it:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1110968

Tested now at the link above.

--Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/