linux-kernel - Re: [PATCH] C6X: add support to build with BINFMT_ELF

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: <CAMjpGUe+CMkHP7owZym_6c2RDvgLzj8t+ZpLBuqQ0euk+ArV2Q@mail.gmail.com>
Date:	Sat, 21 Apr 2012 01:01:04 -0400
From:	Mike Frysinger <vapier.adi@...il.com>
To:	Mark Salter <msalter@...hat.com>
Cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	Alexander Viro <viro@...iv.linux.org.uk>,
	Aurelien Jacquiot <a-jacquiot@...com>,
	Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH] C6X: add support to build with BINFMT_ELF_FDPIC

On Fri, Apr 20, 2012 at 17:47, Mark Salter wrote:
> --- a/arch/c6x/kernel/process.c
> +++ b/arch/c6x/kernel/process.c
>
> +
> +/* Fill in the fpu structure for a core dump. This is easy -- we don't have any */
> +int dump_fpu(struct pt_regs *regs, elf_fpregset_t *fpu)
> +{
> +       /* Not valid */
> +       return 0;
> +}

you could avoid this like Blackfin has:
arch/blackfin/include/asm/elf.h:
#define ELF_CORE_COPY_FPREGS(...) 0     /* Blackfin has no FPU */

> --- a/fs/Kconfig.binfmt
> +++ b/fs/Kconfig.binfmt
>
>  config BINFMT_ELF_FDPIC
>        bool "Kernel support for FDPIC ELF binaries"
>        default y
> -       depends on (FRV || BLACKFIN || (SUPERH32 && !MMU))
> +       depends on (FRV || BLACKFIN || (SUPERH32 && !MMU) || TMS320C6X)

shouldn't the main arch symbol be "C6X" to match arch/c6x/ ?
-mike
--
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/