linux-kernel - Re: [PATCH 4/4] FRV: Fix linux/elf-fdpic.h

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <507BFE70.9020601@metafoo.de>
Date:	Mon, 15 Oct 2012 14:15:44 +0200
From:	Lars-Peter Clausen <lars@...afoo.de>
To:	David Howells <dhowells@...hat.com>
CC:	linux-kernel@...r.kernel.org,
	Fengguang Wu <fengguang.wu@...el.com>, uclinux-dev@...inux.org
Subject: Re: [PATCH 4/4] FRV: Fix linux/elf-fdpic.h

On 10/15/2012 01:44 PM, David Howells wrote:
> It seems I accidentally switched the guard on linux/elf-fdpic.h from #ifdef
> __KERNEL__ to #ifndef __KERNEL__ when attempting to expand the guarded region
> to cover the elf_fdpic_params struct when doing the UAPI split - with the
> result that the struct became unavailable to kernel code.
> 
> Move incorrectly guarded bits back to the kernelspace header.
> 
> Whilst we're at it, the __KERNEL__ guards can be deleted as they're no longer
> necessary.
> 
> Reported-by: Fengguang Wu <fengguang.wu@...el.com>
> Reported-by: Lars-Peter Clausen <lars@...afoo.de>
> Signed-off-by: David Howells <dhowells@...hat.com>
> cc: Fengguang Wu <fengguang.wu@...el.com>
> cc: Lars-Peter Clausen <lars@...afoo.de>
> cc: uclinux-dev@...inux.org
> ---
> 
>  include/uapi/linux/elf-fdpic.h |   42 +++-------------------------------------

>  1 file changed, 3 insertions(+), 39 deletions(-)

The second part of the patch adding it back to include/linux/elf-fdpic.h
seems to be missing.


Thanks,
- Lars
--
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/