From: David Howells <dhowells@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: dhowells@redhat.com, torvalds@osdl.org,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-am33-list@redhat.com
Subject: Re: [PATCH 1/2] Suppress A.OUT library support in ELF binfmt if !CONFIG_BINFMT_AOUT [try #3]
Date: Wed, 07 Nov 2007 23:30:33 +0000 [thread overview]
Message-ID: <1784.1194478233@redhat.com> (raw)
In-Reply-To: <1194473220.11490.93.camel@pmac.infradead.org>
David Woodhouse <dwmw2@infradead.org> wrote:
> Ew, no. This is horridly broken. You should never use CONFIG_xxx_MODULE
> in the static kernel at all -- and you should _especially_ not be using
> it in header files which are exported to userspace.
AOUT support can be mostly built into a module, but a small part of it that is
arch-specific still gets built into the main kernel. *That* is the main thing
that is wrong.
I suppose it might be possible to move those bits of the main kernel into
inline functions in asm/a.out.h and thus include them directly in
binfmt_aout.ko.
> This abomination certainly doesn't seem to have any direct relation to
> mn10300 support -- I think all you really need there is not to attempt
> to export {asm,linux}/a.out.h if asm/a.out.h doesn't exist, which is
> something you haven't attempted here anyway.
No, it's not that simple. If asm/a.out.h doesn't exist, then various bits of
the kernel break that shouldn't. fs/binfmt_elf.c for example. fs/exec.c for
another. They *expect* bits of the asm/a.out.h and linux/a.out.h to exist -
which they shouldn't.
Not exporting them isn't by itself sufficient. The required constants
themselves are not defined for an arch that doesn't have the support, and so
the core code must not depend on them. This patch fixes that.
Furthermore, STACK_TOP and STACK_TOP_MAX don't belong in asm/a.out.h as far as
I can tell. They should probably be wherever TASK_SIZE resides (ie:
asm/processor.h).
David
next prev parent reply other threads:[~2007-11-07 23:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 17:43 [PATCH 0/2] MN10300: Add the MN10300 architecture to Linux kernel [try #3] David Howells
2007-11-07 17:43 ` [PATCH 1/2] Suppress A.OUT library support in ELF binfmt if !CONFIG_BINFMT_AOUT " David Howells
2007-11-07 17:52 ` Mike Frysinger
2007-11-07 22:07 ` David Woodhouse
2007-11-07 23:30 ` David Howells [this message]
2007-11-07 23:54 ` Adrian Bunk
2007-11-08 4:13 ` [PATCH 0/2] MN10300: Add the MN10300 architecture to Linux kernel " Adrian Bunk
2007-11-08 14:00 ` David Howells
2007-11-09 11:02 ` Adrian Bunk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1784.1194478233@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=linux-am33-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox