linux-kernel - Re: [PATCH v9 01/17] h8300: Assembly headers.

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: <20150427092622.GD11048@distanz.ch>
Date:	Mon, 27 Apr 2015 11:26:22 +0200
From:	Tobias Klauser <tklauser@...tanz.ch>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Yoshinori Sato <ysato@...rs.sourceforge.jp>,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org
Subject: Re: [PATCH v9 01/17] h8300: Assembly headers.

On 2015-04-27 at 09:48:39 +0200, Arnd Bergmann <arnd@...db.de> wrote:
> On Monday 27 April 2015 09:42:41 Tobias Klauser wrote:
> > > diff --git a/arch/h8300/include/asm/elf.h b/arch/h8300/include/asm/elf.h
> > > new file mode 100644
> > > index 0000000..09031d0
> > > --- /dev/null
> > > +++ b/arch/h8300/include/asm/elf.h
> > > @@ -0,0 +1,101 @@
> > > +#ifndef __ASM_H8300_ELF_H
> > > +#define __ASM_H8300_ELF_H
> > > +
> > > +/*
> > > + * ELF register definitions..
> > > + */
> > > +
> > > +#include <asm/ptrace.h>
> > > +#include <asm/user.h>
> > > +
> > > +typedef unsigned long elf_greg_t;
> > > +
> > > +#define ELF_NGREG (sizeof(struct user_regs_struct) / sizeof(elf_greg_t))
> > > +typedef elf_greg_t elf_gregset_t[ELF_NGREG];
> > > +typedef unsigned long elf_fpregset_t;
> > > +
> > > +/*
> > > + * This is used to ensure we don't load something for the wrong architecture.
> > > + */
> > > +#define elf_check_arch(x) ((x)->e_machine == EM_H8_300)
> > 
> > EM_H8_300 is still used before it is introduced in patch 15/17, please
> > change the patch order. Otherwise you break bisectability.
> 
> While that is true in principle, I really wouldn't care about that
> when introducing a new architecture: There is no way to use this
> code unless you introduce all code first.

Agreed. But should the ELF machine at least be introduced before the
build infrastructure (patch 10/17) is added? Otherwise we're able to
compile the new arch port in principle but it will fail due to the
missing definition.
--
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/