linux-kernel - Re: [PATCH 1/4] asm/sections: add text/data checking functions for arches to override

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] [day] [month] [year] [list]

Message-Id: <20090623190426.d4cc9853.akpm@linux-foundation.org>
Date:	Tue, 23 Jun 2009 19:04:26 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Mike Frysinger <vapier.adi@...il.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...hat.com,
	rgetz@...ckfin.uclinux.org
Subject: Re: [PATCH 1/4] asm/sections: add text/data checking functions for
  arches to override

On Tue, 23 Jun 2009 21:48:03 -0400 Mike Frysinger <vapier.adi@...il.com> wrote:

> > I suppose that for completeness and consistency etc really we should have
> >
> > #define arch_is_kernel_text arch_is_kernel_text
> > #define arch_is_kernel_data arch_is_kernel_data
> >
> > in here.
> 
> *shrug* other places that use this style dont include these defines
> for completeness

Examples?

All the ones I can find do things like

#ifndef vmcore_elf_check_arch_cross
#define vmcore_elf_check_arch_cross(x) 0
#endif

> as the define muck is for the header to know about
> (arches providing their own version), not any source code -- they
> shouldnt know anything about the ifdef stuff.

Failing to do the #define will have various tricky failure modes.  But
it's more a question of "what is the _right_ thing to do", then doing
that consistently.

>  i dont care much either way.

Someone has to.
--
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/